From: Sam Ravnborg <sam@ravnborg.org>
To: Dave Dillow <dave@thedillows.org>
Cc: Sam Ravnborg <sam@ravnborg.org>,
Linux-Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Is the 2.6 dependency information complete? Doesn't look so...
Date: Tue, 2 Mar 2004 19:07:30 +0100 [thread overview]
Message-ID: <20040302180730.GD2135@mars.ravnborg.org> (raw)
In-Reply-To: <1078163528.22900.17.camel@dillow.idleaire.com>
On Mon, Mar 01, 2004 at 12:52:08PM -0500, Dave Dillow wrote:
>
> Also, the changesets at bk://typhoon.bkbits.net/autoget-2.5 add
> functionality to kbuild to checkout needed files automatically, as the
> build progresses -- no more 'bk get' needed...
>
> I haven't kept it up to date, but I doubt it'd need many changes to work
> with a recent kernel. It's currently BK/SCCS specific, but I do not
> think it would be hard to make it work with other version control
> systems, as long as make supports them.
>
> Since you do so much in kbuild, I'd love some comments on it, if you
> have time.
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?
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".
Sam
next prev parent reply other threads:[~2004-03-02 18:06 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 [this message]
2004-03-02 18:40 ` [PATCH 0/3] Auto checkout for kbuild Dave Dillow
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=20040302180730.GD2135@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=dave@thedillows.org \
--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.