From: Ricky Beam <jfbeam@bluetronic.net>
To: David Dillow <dave@thedillows.org>
Cc: Linux Kernel Mail List <linux-kernel@vger.kernel.org>,
<kbuild-devel@lists.sourceforge.net>
Subject: Re: [BK PATCH 0/3] Teach kbuild to pull files from BK repository
Date: Sun, 7 Dec 2003 22:06:05 -0500 (EST) [thread overview]
Message-ID: <Pine.GSO.4.33.0312072204020.13188-100000@sweetums.bluetronic.net> (raw)
In-Reply-To: <1070595121.4574.24.camel@ori.thedillows.org>
On 4 Dec 2003, David Dillow wrote:
>I finally got tired of having to run "bk -r get" before doing a build, so I
...
This is not necessary...
spacemeat:/usr/src/linux-2.6-bk# cat BitKeeper/etc/config
# Don't change this unless you're Linus
logging_ask:no
description: Linux kernel tree
logging: logging@openlogging.org
email: torvalds@transmeta.com
# cramer / why isn't this the default?
[]checkout:get
That last line is the magic. It's documented in the BK FAQ (more than once
I think.)
--Ricky
next prev parent reply other threads:[~2003-12-08 3:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-05 3:32 [BK PATCH 0/3] Teach kbuild to pull files from BK repository David Dillow
2003-12-08 3:06 ` Ricky Beam [this message]
2003-12-08 15:12 ` David Dillow
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=Pine.GSO.4.33.0312072204020.13188-100000@sweetums.bluetronic.net \
--to=jfbeam@bluetronic.net \
--cc=dave@thedillows.org \
--cc=kbuild-devel@lists.sourceforge.net \
--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 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).