From: Linus Torvalds <torvalds@linux-foundation.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Michal Simek <michal.simek@petalogix.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] arch/microblaze fixes for 2.6.35-rc3 v2
Date: Tue, 8 Jun 2010 17:29:06 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.2.00.1006081720060.4506@i5.linux-foundation.org> (raw)
In-Reply-To: <AANLkTikeD21EtwtASzj8RksDqZyEof_kmUTnNr2HwwU2@mail.gmail.com>
On Tue, 8 Jun 2010, Geert Uytterhoeven wrote:
>
> Seems like you will have written more angry emails than there will be
> new commits in 2.6.35-rc3 ;-)
Well, partly in order to be fair. I did consider letting architectures
like microblaze just off the hook entirely - it's not like it will affect
a lot of people. But at the same time, I don't want to be in the situation
that some people get to send me patches just because I don't happen to
think that their changes will matter to most others.
And at this stage, I'd rather be too strict than too lenient. If -rc3 has
no new regressions, and fixes the ones that hit people worst, I'll be very
happy. I can be more open to patches after I get back, if it turns out
that I was _too_ strict for -rc3.
As to the number of "no, I won't take it" emails, I suspect a large part
of that is simply because most developers (understandably) do not read
lkml, stauing mostly on the development lists that are more specific to
their particular area. As a result, there's no real way to reliably reach
people, and I end up sending basically the same message several times.
Which obviously tends to also then make the messages more cross ;)
Linus
next prev parent reply other threads:[~2010-06-09 0:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-07 18:20 Michal Simek
2010-06-07 23:31 ` FUJITA Tomonori
2010-06-08 10:28 ` Michal Simek
2010-06-08 11:03 ` FUJITA Tomonori
2010-06-08 20:14 ` Linus Torvalds
2010-06-08 20:36 ` Geert Uytterhoeven
2010-06-09 0:29 ` Linus Torvalds [this message]
2010-06-09 11:04 ` Michal Simek
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=alpine.LFD.2.00.1006081720060.4506@i5.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@petalogix.com \
/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
Powered by JetHome