All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Dan Aloni <da-x@gmx.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: auto-bk-get
Date: Fri, 11 Jul 2003 08:43:58 -0400	[thread overview]
Message-ID: <3F0EB10E.6070500@pobox.com> (raw)
In-Reply-To: <20030711052539.GA9586@callisto.yi.org>

Dan Aloni wrote:
> 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.
>>>
>>>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). 
>>
>>
>>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.
> 
> 
> It's not just that. Does make and the build system alone allow you 
> to build in an entirely different tree? (i.e check out and recreate
> the directory structure somewhere else, leaving the repository clean or
> even on a read-only media).


Yes, that's Sam Ravnborg's (sp?) srcdir != objdir work.

	Jeff




  reply	other threads:[~2003-07-11 12:32 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     ` Jeff Garzik [this message]
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=3F0EB10E.6070500@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=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 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.