From: Roger Gammans <roger@computer-surgery.co.uk>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Dan Aloni <da-x@gmx.net>, linux-kernel@vger.kernel.org
Subject: Re: auto-bk-get
Date: Mon, 14 Jul 2003 23:06:01 +0100 [thread overview]
Message-ID: <20030714220601.GA31384@computer-surgery.co.uk> (raw)
In-Reply-To: <3F0DD5F6.5060302@pobox.com>
[-- Attachment #1: Type: text/plain, Size: 1138 bytes --]
On Thu, Jul 10, 2003 at 05:09:10PM -0400, Jeff Garzik wrote:
> Dan Aloni wrote:
> >For kernel developers which are BitKeeper users,
> >
> >auto-bk-get is an on-demand 'bk get' libc wrapper tool.
> [snip]
>
> No offense, but, it would probably be easier to fix the few remaining
> places where the makefile system does not automatically check out the files.
>
> It works great for everything except the Kconfig stuff, IIRC.
I played about with this a long time ago at the beginning of
2.5, so was attempt to do this with the old build system which
didn't had a few awkward bits, and then I was distracted by userspace
stuff.
What I did I put here ( http://www.sandman.uklinux.net/odds/index.html )
it might be of use - though as I recall correctly most of the
code was taken from patch(1). So it's nothing special.
TTFN
--
Roger. Home| http://www.sandman.uklinux.net/
Master of Peng Shui. (Ancient oriental art of Penguin Arranging)
Work|Independent Systems Consultant | http://www.firstdatabase.co.uk/
So what are the eigenvalues and eigenvectors of 'The Matrix'? --anon
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
prev parent reply other threads:[~2003-07-14 21:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-10 18:44 auto-bk-get Dan Aloni
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 ` Roger Gammans [this message]
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=20030714220601.GA31384@computer-surgery.co.uk \
--to=roger@computer-surgery.co.uk \
--cc=da-x@gmx.net \
--cc=jgarzik@pobox.com \
--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