Attracting reviewers in your patch series

Usually faster the number of commits, faster the development process. But development without strict reviewing doesn’t guarantee quality on the code. Unfortunately, rarely you will see people willing or even just being able to review the changes you are proposing. Attract reviewers is hard!

Lemma:
The art of writing a good patch series is all about to attract reviewers.

Proof is omitted due to lack of space. Sorry ;)

I’d start to write a post about how to write a nice commit message and patch series, so I could use as a future reference for you.

( Note I’m not judging that you are often writing patches wrongly. I’m just trying let you aware that you can do it much better so your changes can go smoothly in the project. )

However a quick search showed that Peter already did a nice post about it. Please take a look there. I recommend (signed-off-by)!

Advertisements

Tags: , , ,

2 Responses to “Attracting reviewers in your patch series”

  1. Benjamin Otte Says:

    I think the art of writing a patch series is also about making bisection easy when the inevitable bug shows up later.

  2. vignatti Says:

    That’s implicit :)

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s


%d bloggers like this: