From: Dave Jones <davej@codemonkey.org.uk>
To: Greg KH <greg@kroah.com>
Cc: "Martin J. Bligh" <mbligh@aracnet.com>,
Linus Torvalds <torvalds@transmeta.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Summit support for 2.5 [0/4]
Date: Sun, 13 Oct 2002 22:31:33 +0100 [thread overview]
Message-ID: <20021013213133.GA11769@suse.de> (raw)
In-Reply-To: <20021013211740.GC24140@kroah.com>
On Sun, Oct 13, 2002 at 02:17:40PM -0700, Greg KH wrote:
> > I *will* do that. Just not in time for the freeze. IMHO, that's a cleanup (and yes,
> > a needed one).
>
> Hm, IMVHO I think this should be done correctly, as a subarch, instead
> of just patches (although your patches are split up very nicely, good
> job, that couldn't have been very easy.) I don't know if "Time" is a
> good excuse to put things like this in the tree, in the format that it
> shouldn't be.
>
> But as I'm not the i386 maintainer, I'll let Linus decide that one :)
If half-arsed stuff is going to get merged just to beat the freeze,
maybe it should go in with the constraint "get it cleaned by xxx
or it gets dropped".
Personally, I agree with Greg, and that it should get fixed up
_before_ the freeze. Fixing this up to work with subarch's shouldn't
take *that* long, and there's *counts* a whole week remaining before
Linus goes on hols 8-)
Dave
--
| Dave Jones. http://www.codemonkey.org.uk
next prev parent reply other threads:[~2002-10-13 21:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-13 20:41 Martin J. Bligh
2002-10-13 20:59 ` Greg KH
2002-10-13 21:06 ` Martin J. Bligh
2002-10-13 21:17 ` Greg KH
2002-10-13 21:31 ` Dave Jones [this message]
2002-10-13 22:15 ` Linus Torvalds
2002-10-14 2:02 ` Martin J. Bligh
2002-10-14 2:25 ` Greg KH
2002-10-14 2:49 ` Kai Germaschewski
2002-10-14 3:02 ` Greg KH
2002-10-14 5:46 ` Eric W. Biederman
2002-10-14 3:09 ` Martin J. Bligh
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=20021013213133.GA11769@suse.de \
--to=davej@codemonkey.org.uk \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
--cc=torvalds@transmeta.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
all inboxes | Powered by JetHome®