From: Larry McVoy <lm@bitmover.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Larry McVoy <lm@bitmover.com>, Paul Mackerras <paulus@samba.org>,
linuxppc-dev@lists.linuxppc.org
Subject: Re: 2.5 development
Date: Fri, 15 Feb 2002 15:53:52 -0800 [thread overview]
Message-ID: <20020215155352.H32005@work.bitmover.com> (raw)
In-Reply-To: <20020215185016.GQ2004@opus.bloom.county>; from trini@kernel.crashing.org on Fri, Feb 15, 2002 at 11:50:16AM -0700
> So are out of order changesets on the horizon?
That depends on the height of the mountain on which you are standing. :-)
They are a ways out, you'll need to change your workflow a bit until we
get them. Jeff Garzik is going to take a pass at a Documentation/bk-howto
this weekend which will describe how he does it. The reports from Linus
are that if you are willing to work like Jeff, it does save Linus quite a
bit of work.
--
---
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:[~2002-02-15 23:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-15 12:11 2.5 development Paul Mackerras
2002-02-15 16:40 ` Tom Rini
2002-02-15 16:58 ` Larry McVoy
2002-02-15 17:01 ` Jeff Garzik
2002-02-15 17:06 ` Larry McVoy
2002-02-15 17:17 ` Larry McVoy
2002-02-15 17:32 ` Tom Rini
2002-02-15 17:33 ` Larry McVoy
2002-02-15 17:36 ` Tom Rini
2002-02-15 18:44 ` Larry McVoy
2002-02-15 18:50 ` Tom Rini
2002-02-15 23:53 ` Larry McVoy [this message]
[not found] <p05100300b8a144d7cf05@[66.26.75.241]>
2002-02-26 15:51 ` Stefan Jeglinski
2002-02-26 16:13 ` Tom Rini
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=20020215155352.H32005@work.bitmover.com \
--to=lm@bitmover.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@samba.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).