From: David Dillow <firstname.lastname@example.org>
To: Ricky Beam <email@example.com>
Cc: Linux Kernel Mail List <firstname.lastname@example.org>,
Subject: Re: [BK PATCH 0/3] Teach kbuild to pull files from BK repository
Date: 08 Dec 2003 10:12:58 -0500 [thread overview]
Message-ID: <email@example.com> (raw)
On Sun, 2003-12-07 at 22:06, Ricky Beam wrote:
> 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...
> # cramer / why isn't this the default?
> That last line is the magic. It's documented in the BK FAQ (more than once
> I think.)
Yes, and most of my repositories are set that way. But I like having the
option of not needing that line, and it was interesting to see how to
make it work properly.
Besides, it still does the get, just at a clone/pull time, and you have
gobs of extra files laying around.
prev parent reply other threads:[~2003-12-08 15:13 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
2003-12-08 15:12 ` David Dillow [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).