[Ksummit-discuss] [TOPIC] Encouraging more reviewers
tiwai at suse.de
Sun Jun 1 08:36:28 UTC 2014
At Sat, 31 May 2014 18:49:51 +0200,
Geert Uytterhoeven wrote:
> On Wed, May 28, 2014 at 11:59 PM, Thomas Gleixner <tglx at linutronix.de> wrote:
> > I really started to put breaks into this cycle of hell, where I get
> > spammed with a 30+ patch series in the morning and after I spent some
> > quality time looking at it and replying to a particular patch, I get
> > another spam bomb within a few hours, which is not much better than
> > the previous one.
> That's indeed an issue. Some large series are immediately reposted for every
> single (sometimes trivial) change suggested by a commenter.
> This also leads to inflated patch version numbers. I'm already getting nervous
> when I have to send out a v3 or v4 myself, but from a quick search, v29
> seems to be the current record on lkml...
> Does git send-email remember when the previous version of a series was
> sent out?
> If yes, it could refuse to resend it too soon. The back off period would
> depend on the size of the patch series (large patch series need more delay).
IMO, it's dangerous to let a basic tool like git blocking the
immediate resend, too.
I agree that digesting a large patchset is one of most painful tasks
as a maintainer. In such a case, however, I'd rather suggest to split
the large patch series into multiple staged patchsets.
More information about the Ksummit-discuss