From: Andrew Morton <akpm@linux-foundation.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linus <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Lucas De Marchi <lucas.demarchi@profusion.mobi>
Subject: Re: large cross tree spelling fixes
Date: Thu, 28 Apr 2011 23:31:11 -0700 [thread overview]
Message-ID: <20110428233111.3ca7b04f.akpm@linux-foundation.org> (raw)
In-Reply-To: <20110428130427.06925753.sfr@canb.auug.org.au>
On Thu, 28 Apr 2011 13:04:27 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Linus,
>
> Next time you are tempted to take one of these, please resist. :-)
>
> It was not urgent, could have been (at least) broken up and sent to the
> respective maintainers, and caused many conflicts in linux-next (which
> either means unnecessary rebases/merges or you will see the conflicts
> next merge window).
Probably the best time for this sort of thing is immediately after
-rc1, when everyone's out-of-tree trees are the smallest.
next prev parent reply other threads:[~2011-04-29 6:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-28 3:04 large cross tree spelling fixes Stephen Rothwell
2011-04-29 6:31 ` Andrew Morton [this message]
2011-04-29 14:08 ` Lucas De Marchi
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=20110428233111.3ca7b04f.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucas.demarchi@profusion.mobi \
--cc=sfr@canb.auug.org.au \
--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