From: Larry McVoy <lm@bitmover.com>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: 2.5 development
Date: Fri, 15 Feb 2002 08:58:12 -0800 [thread overview]
Message-ID: <20020215085812.Z8353@work.bitmover.com> (raw)
In-Reply-To: <15468.64269.8252.644104@argo.ozlabs.ibm.com>; from paulus@samba.org on Fri, Feb 15, 2002 at 11:11:57PM +1100
On Fri, Feb 15, 2002 at 11:11:57PM +1100, Paul Mackerras wrote:
> The current limitations of BK mean that we will not be able to take
> changesets directly from the linuxppc-2.5 tree and send them to
> Linus.
You can export changes as a patch and import them. Notice that the new
"bk comments" command will let you change the comments after you do the
import. To get a changeset's comments in a form that bk comments will
like, try this (requires bk 2.1.4 or later):
bk changes -r+ -vnd'### Change the comments to :GFILE: below\n:C:'
That will do it for the most recent changeset, s/+/rev/ that you used
with the export/import.
--
---
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 16:58 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 [this message]
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
[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=20020215085812.Z8353@work.bitmover.com \
--to=lm@bitmover.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@samba.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.