From: Larry McVoy <lm@bitmover.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Tom Rini <trini@kernel.crashing.org>,
Iain Sandoe <iain@sandoe.co.uk>,
linuxppc-dev@lists.linuxppc.org
Subject: Re: status of ppc support in official 2.4.0 or Alan's 2.4.0-ac1
Date: Mon, 8 Jan 2001 09:14:45 -0800 [thread overview]
Message-ID: <20010108091445.C3077@work.bitmover.com> (raw)
In-Reply-To: <Pine.LNX.4.05.10101081753120.30839-100000@callisto.of.borg>
On Mon, Jan 08, 2001 at 05:54:00PM +0100, Geert Uytterhoeven wrote:
> It may help to create nightly diffs between Linus' 2.4.0 and linuxppc_2_4 and
> put them on some FTP site.
bk help export
you want
bk export -tpatch
Cort's been using it for a year or more to send Linus patches.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-01-08 17:14 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-08 16:16 status of ppc support in official 2.4.0 or Alan's 2.4.0-ac1 Iain Sandoe
2001-01-08 16:32 ` Tom Rini
2001-01-08 16:54 ` Geert Uytterhoeven
2001-01-08 17:03 ` Tom Rini
2001-01-08 17:14 ` Larry McVoy [this message]
2001-01-08 17:20 ` Geert Uytterhoeven
-- strict thread matches above, loose matches on Subject: below --
2001-01-09 23:45 Iain Sandoe
2001-01-10 1:09 ` Derek Homeier
[not found] <3A59C65F.D92C79E8@pop.agri.ch>
2001-01-09 22:28 ` Derek Homeier
2001-01-08 14:48 Iain Sandoe
2001-01-09 22:39 ` Derek Homeier
[not found] <200101070559.XAA14527@lists.linuxppc.org>
2001-01-08 13:35 ` Derek Homeier
2001-01-08 14:15 ` Ethan Benson
2001-01-05 14:55 Kevin B. Hendricks
2001-01-05 15:37 ` Tom Rini
2001-01-06 0:40 ` Ethan Benson
2001-01-06 14:18 ` Michel Dänzer
2001-01-06 14:59 ` Ethan Benson
2001-01-06 17:42 ` Tom Rini
2001-01-06 18:22 ` Tony Mantler
2001-01-08 15:07 ` Kaoru Fukui
2001-01-08 15:37 ` Tom Rini
2001-01-06 17:35 ` Olaf Hering
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=20010108091445.C3077@work.bitmover.com \
--to=lm@bitmover.com \
--cc=geert@linux-m68k.org \
--cc=iain@sandoe.co.uk \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=trini@kernel.crashing.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.