From: Borislav Petkov <bp@alien8.de>
To: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
Cc: Thomas Gleixner <tglx@linutronix.de>,
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 18:46:52 +0100 [thread overview]
Message-ID: <20141213174652.GD29934@pd.tnic> (raw)
In-Reply-To: <20141213135231.5684cf9d@lxorguk.ukuu.org.uk>
On Sat, Dec 13, 2014 at 01:52:31PM +0000, One Thousand Gnomes wrote:
...
> It could then be integrated into git (if only so we can have a "git lost"
> command to block annoying sources)
All sounds nice and good but I'd be fine with people adhering to the
one-week feedback gather rule and not sending patchsets during the merge
window, for starters. I think those two will get us pretty far.
> 2. Is X86 moving at a rate which needs some additional maintainers to
> "maintain" the pending queue during merge windows and the like, and get
> stuff into order for the maintainers proper ?
Yep, no patches during the merge window should be a good start.
The rest of the time x86 actually scales pretty fine IMO.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2014-12-13 17:47 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
2014-12-13 13:52 ` One Thousand Gnomes
2014-12-13 17:46 ` Borislav Petkov [this message]
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=20141213174652.GD29934@pd.tnic \
--to=bp@alien8.de \
--cc=akpm@linux-foundation.org \
--cc=gnomes@lxorguk.ukuu.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox