From: Rusty Russell <rusty@rustcorp.com.au>
To: Andrew Morton <akpm@osdl.org>
Cc: lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [TRIVIAL] doc update for bk usage
Date: Thu, 20 May 2004 17:08:06 +1000 [thread overview]
Message-ID: <1085036543.24931.154.camel@bach> (raw)
From: carbonated beverage <ramune@net-ronin.org>
---
bk://... appears to be dead, use http://... instead.
===== Documentation/BK-usage/bk-kernel-howto.txt 1.7 vs edited =====
--- trivial-2.6.6-bk6/Documentation/BK-usage/bk-kernel-howto.txt.orig 2004-05-20 15:59:35.000000000 +1000
+++ trivial-2.6.6-bk6/Documentation/BK-usage/bk-kernel-howto.txt 2004-05-20 15:59:35.000000000 +1000
@@ -279,5 +279,5 @@
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`,+
+ bk export -tpatch -r`bk repogca http://linux.bkbits.net/linux-2.5`,+
--- trivial-2.6.6-bk6/Documentation/BK-usage/gcapatch.orig 2004-05-20 15:59:35.000000000 +1000
+++ trivial-2.6.6-bk6/Documentation/BK-usage/gcapatch 2004-05-20 15:59:35.000000000 +1000
@@ -5,4 +5,4 @@
# Usage: gcapatch > foo.patch
#
-bk export -tpatch -hdu -r`bk repogca bk://linux.bkbits.net/linux-2.5`,+
+bk export -tpatch -hdu -r`bk repogca http://linux.bkbits.net/linux-2.5`,+
--
What is this? http://www.kernel.org/pub/linux/kernel/people/rusty/trivial/
Don't blame me: the Monkey is driving
File: carbonated beverage <ramune@net-ronin.org>: doc update for bk usage
next reply other threads:[~2004-05-20 7:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-20 7:08 Rusty Russell [this message]
2004-05-20 8:01 ` [TRIVIAL] doc update for bk usage Jeff Garzik
2004-05-20 8:36 ` Rusty Russell
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=1085036543.24931.154.camel@bach \
--to=rusty@rustcorp.com.au \
--cc=akpm@osdl.org \
--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 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.