From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.25-rc8
Date: Wed, 2 Apr 2008 11:23:55 +1100 [thread overview]
Message-ID: <20080402112355.c86d9eda.sfr@canb.auug.org.au> (raw)
In-Reply-To: <alpine.LFD.1.00.0804011257310.14670@woody.linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 803 bytes --]
On Tue, 1 Apr 2008 13:08:57 -0700 (PDT) Linus Torvalds <torvalds@linux-foundation.org> wrote:
>
> A lot of the one-liners are some sparse cleanups, which is probably
> unnecessary noise at this point, but when Al sends me a series I just tend
> to apply it because his patches tend to be rather careful and basically
> always correct.
The downside is that at least some of these were already pending in
maintainers trees for 2.6.26 (among other changes) and so have now caused
(unnecessary) merge conflicts. Is there some reason that these fixes
can't go through the subsystem trees (especially once we get past rc1 (or
2) and people are gearing up for the next merge window)?
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-04-02 0:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-01 20:08 Linus Torvalds
2008-04-01 21:42 ` Paul Mackerras
2008-04-02 14:50 ` Linus Torvalds
2008-04-02 18:54 ` Adrian Bunk
2008-04-03 4:08 ` Paul Mackerras
2008-04-03 12:55 ` Josh Boyer
2008-04-03 18:18 ` Sam Ravnborg
2008-04-02 0:23 ` Stephen Rothwell [this message]
2008-04-02 3:03 ` Linus Torvalds
2008-04-02 3:09 ` Linus Torvalds
2008-04-02 18:57 ` Adrian Bunk
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=20080402112355.c86d9eda.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®