From: Borislav Petkov <bp@alien8.de>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Maintainer abuse
Date: Sat, 13 Dec 2014 00:43:36 +0100 [thread overview]
Message-ID: <20141212234336.GA28451@pd.tnic> (raw)
In-Reply-To: <alpine.DEB.2.11.1412130016090.16494@nanos>
On Sat, Dec 13, 2014 at 12:24:03AM +0100, Thomas Gleixner wrote:
> - Posting of massive patch sets right during or just before the merge
> window
>
> - Reposting of patchsets before the reviewer/maintainer had a chance
> to reply to ALL of N patches
Absolutely agreed.
The rule of sending out patches and collecting feedback for a week at
least is not really being respected, from my experience. Shit gets
blasted out at the highest rate possible. Maybe lkml should have a
git-send-email throttle.
And I have the sneaking impression that a lot of people have not really
understood what merge window means.
> Yours grumpy
And then they wonder why reviewers/maintainers are grumpy.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2014-12-12 23:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 23:24 Maintainer abuse Thomas Gleixner
2014-12-12 23:43 ` Borislav Petkov [this message]
2014-12-13 13:52 ` One Thousand Gnomes
2014-12-13 17:46 ` Borislav Petkov
2014-12-15 11:15 ` Thomas Gleixner
2014-12-16 2:47 ` Brian Norris
2014-12-18 10:14 ` patch tracking tools (was Re: Maintainer abuse) Paolo Bonzini
2014-12-18 13:25 ` Fam Zheng
2014-12-19 11:30 ` Paolo Bonzini
2014-12-16 8:06 ` Maintainer abuse Benjamin Herrenschmidt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141212234336.GA28451@pd.tnic \
--to=bp@alien8.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.