From: Jeff Garzik <jgarzik@pobox.com>
To: torvalds@transmeta.com
Cc: linux-kernel@vger.kernel.org
Subject: [BK+PATCH] mention useful BK tip
Date: Sun, 11 May 2003 14:48:55 -0400 [thread overview]
Message-ID: <20030511184855.GA14317@gtf.org> (raw)
Linus, please do a
bk pull bk://kernel.bkbits.net/jgarzik/misc-2.5
This will update the following files:
Documentation/BK-usage/bk-kernel-howto.txt | 8 ++++++++
1 files changed, 8 insertions(+)
through these ChangeSets:
<jgarzik@redhat.com> (03/05/11 1.1105)
[bk] add useful tip to bk kernel howto
Kudos to Wayne Scott @ BitMover for this.
diff -Nru a/Documentation/BK-usage/bk-kernel-howto.txt b/Documentation/BK-usage/bk-kernel-howto.txt
--- a/Documentation/BK-usage/bk-kernel-howto.txt Sun May 11 14:48:13 2003
+++ b/Documentation/BK-usage/bk-kernel-howto.txt Sun May 11 14:48:13 2003
@@ -273,3 +273,11 @@
A tag is just an alias for a specific changeset... and since changesets
are ordered, a tag is thus a marker for a specific point in time (or
specific state of the tree).
+
+
+3) Is there an easy way to generate One Big Patch versus mainline,
+ for my long-lived kernel branch?
+A. Yes. This requires BK 3.x, though.
+
+ bk export -tpatch -r`bk repogca bk://linux.bkbits.net/linux-2.5`,+
+
reply other threads:[~2003-05-11 18:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030511184855.GA14317@gtf.org \
--to=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--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®