From: Dave Dillow <dave@thedillows.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Linux-Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/3] Auto checkout for kbuild
Date: Tue, 02 Mar 2004 13:40:02 -0500 [thread overview]
Message-ID: <1078252801.31314.21.camel@dillow.idleaire.com> (raw)
In-Reply-To: <20040302180730.GD2135@mars.ravnborg.org>
On Tue, 2004-03-02 at 13:07, Sam Ravnborg wrote:
> I have pulled the tree, and the getfiles script and Makefile.repo is easy to spot.
> Could you drop a mail with the rest of your changes as a regular patch?
Here's three patches, in order. The first adds getfiles and
Makefile.repo. It will pull all files needed from BK, except for the
Kconfig files.
The second adds support for Kconfig files.
The third is just some comsetic cleanups to cut chatter during
non-verbose builds.
> I will then try to look through what you made - but my first impression is that this
> is by far too much overhead just to replace an "bk -r co -Sq".
There is a bit of overhead, but mainly for files that are not there. If
the file has already been checked out, and the SCCS file is not newer,
then getfiles will not be run. There is the matter of an extra stat()
call, though, to figure that out.
For me, since I am working in a NFS directory, this is much faster than
doing a "bk -r get; make bzImage" because it only pulls the files needed
to build my kernel configuration. Even on a local disk, it "feels"
faster, though I'm sure I do not see as much of a benefit.
Code wise, yeah, it is more overhead, and it could be potentially
fragile in regards to compiler messages in the getfiles script.
--
Dave Dillow <dave@thedillows.org>
prev parent reply other threads:[~2004-03-02 18:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-29 23:51 Is the 2.6 dependency information complete? Doesn't look so Matthias Andree
2004-02-29 23:59 ` Måns Rullgård
2004-03-01 6:08 ` Sam Ravnborg
2004-03-01 17:52 ` Dave Dillow
2004-03-02 18:07 ` Sam Ravnborg
2004-03-02 18:40 ` Dave Dillow [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=1078252801.31314.21.camel@dillow.idleaire.com \
--to=dave@thedillows.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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
all inboxes | Powered by JetHome®