From: Dan Aloni <da-x@gmx.net>
To: linux-kernel@vger.kernel.org
Subject: auto-bk-get
Date: Thu, 10 Jul 2003 21:44:29 +0300 [thread overview]
Message-ID: <20030710184429.GA28366@callisto.yi.org> (raw)
For kernel developers which are BitKeeper users,
auto-bk-get is an on-demand 'bk get' libc wrapper tool.
It means that you don't need to run 'bk -r get' in order to build
the kernel. Instead, you just run 'make config' or 'make bzImage',
using auto-bk-get in a clean repository and auto-bk-get will
only 'bk get' the files you need from the repository (one of my
test cases showed only 2800 out of 14000 files were checked out).
It also supports building in an entirely different directory,
taking the files from a repository somewhere else.
To download and compile auto-bk-get:
# bk clone http://auto-bk-get.bkbits.net/auto-bk-get
# cd auto-bk-get
# make
Read the README file.
--
Dan Aloni
da-x@gmx.net
next reply other threads:[~2003-07-10 18:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-10 18:44 Dan Aloni [this message]
2003-07-10 21:09 ` auto-bk-get Jeff Garzik
2003-07-11 5:25 ` auto-bk-get Dan Aloni
2003-07-11 12:43 ` auto-bk-get Jeff Garzik
2003-07-14 22:06 ` auto-bk-get Roger Gammans
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=20030710184429.GA28366@callisto.yi.org \
--to=da-x@gmx.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).