From: Tom Rini <trini@kernel.crashing.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4test-ac merge status
Date: Sat, 30 Dec 2000 19:40:31 -0700 [thread overview]
Message-ID: <20001230194031.C4703@opus.bloom.county> (raw)
In-Reply-To: <20001230192737.B4703@opus.bloom.county> <E14CYJk-0007PG-00@the-village.bc.nu>
In-Reply-To: <E14CYJk-0007PG-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Sun, Dec 31, 2000 at 02:33:50AM +0000
On Sun, Dec 31, 2000 at 02:33:50AM +0000, Alan Cox wrote:
> > I'm sure at least a few people want to know where the PowerPC port falls in
> > all of that. :)
> >
> > ...hopeing we aren't in the bitbucket..
>
> It might be the ppc port is 2.4.0ac1 and 2.4.2 Linus or something. I don't think
> that is likely to be a big problem. I need to get on top of 2.2.19pre4 and
> the rest of the Linus resync then I'm going to dump chunks of stuff out of
> -ac and try and get a nice clean -ac tree. If folks want to sync non x86
> ports with that initially go ahead.
Oh well. I guess our problem is we can never get Linus to notice the smaller
chunks and he always seems to hate big patches.
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2000-12-31 3:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-31 2:17 Linux 2.4test-ac merge status Alan Cox
2000-12-31 2:27 ` Tom Rini
2000-12-31 2:33 ` Alan Cox
2000-12-31 2:40 ` Tom Rini [this message]
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=20001230194031.C4703@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.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