From: Borislav Petkov <bp@alien8.de>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: Kevin Cernekee <cernekee@gmail.com>,
Jonathan Corbet <corbet@lwn.net>,
Thomas Gleixner <tglx@linutronix.de>,
gnomes@lxorguk.ukuu.org.uk,
Brian Norris <computersforpeace@gmail.com>,
torvalds@linux-foundation.org,
Andrew Morton <akpm@linux-foundation.org>,
linux-doc@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC 0/4] Stop maintainer abuse
Date: Wed, 17 Dec 2014 10:52:27 +0100 [thread overview]
Message-ID: <20141217095227.GA8457@pd.tnic> (raw)
In-Reply-To: <20141217051424.GZ17575@thunk.org>
On Wed, Dec 17, 2014 at 12:14:24AM -0500, Theodore Ts'o wrote:
> And what's wrong for one maintainer will be right for another, and
> vice versa.
Ok, so what's wrong with "should not expect any feedback during the
merge window"?
If they get it, then that's fine. The formulation is loose on purpose.
And besides, when one starts working with maintainers, one soon learns
when they are the busiest and can refrain from sending patchsets then.
Or should we have subsystem maintainers each state whether they wanna
do patchsets during the merge window or not? Or are we bikeshedding
already?
I see your point that different maintainers can be busy at different
times but you also have to acknowledge the desire of some maintainers
not to get new patchsets during the merge window. So we have to have a
way to communicate that to submitters so that no explosions happen.
Oh, and also the
not-resend-in-under-a-week-and-wait-out-complete-review-first rule.
That's my personal pet peeve.
Ha, this sounds like a KS topic :-P
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2014-12-17 9:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-15 6:09 [RFC 0/4] Stop maintainer abuse Kevin Cernekee
2014-12-15 6:09 ` [RFC 1/4] Documentation: Change policy on sending patches during merge window Kevin Cernekee
2014-12-15 8:29 ` Christoph Hellwig
2014-12-15 6:09 ` [RFC 2/4] Documentation/SubmitChecklist: Remind submitters to check the " Kevin Cernekee
2014-12-15 10:17 ` Borislav Petkov
2014-12-16 6:48 ` Kalle Valo
2014-12-15 6:09 ` [RFC 3/4] Documentation: Add cutoff periods for patch acceptance Kevin Cernekee
2014-12-15 10:15 ` Borislav Petkov
2014-12-15 14:59 ` One Thousand Gnomes
2014-12-15 18:29 ` Linus Torvalds
2014-12-15 6:09 ` [RFC 4/4] Documentation: Provide suggestions on when to repost patches Kevin Cernekee
2014-12-15 10:13 ` Borislav Petkov
2014-12-16 18:09 ` [RFC 0/4] Stop maintainer abuse Jonathan Corbet
2014-12-16 20:35 ` Theodore Ts'o
2014-12-16 22:19 ` Kevin Cernekee
2014-12-16 22:31 ` Borislav Petkov
2014-12-17 5:14 ` Theodore Ts'o
2014-12-17 9:52 ` Borislav Petkov [this message]
2014-12-18 19:05 ` Mark Brown
2014-12-18 10:35 ` Paolo Bonzini
2014-12-18 10:42 ` Borislav Petkov
2014-12-18 10:53 ` Paolo Bonzini
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=20141217095227.GA8457@pd.tnic \
--to=bp@alien8.de \
--cc=akpm@linux-foundation.org \
--cc=cernekee@gmail.com \
--cc=computersforpeace@gmail.com \
--cc=corbet@lwn.net \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox