From: David Woodhouse <dwmw2@infradead.org>
To: Ben Greear <greearb@candelatech.com>
Cc: Larry McVoy <lm@bitmover.com>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4 and BitKeeper
Date: Fri, 15 Mar 2002 11:10:41 +0000 [thread overview]
Message-ID: <2865.1016190641@redhat.com> (raw)
In-Reply-To: <3C90E994.2030702@candelatech.com>
In-Reply-To: <3C90E994.2030702@candelatech.com> <Pine.LNX.4.21.0203140141450.4725-100000@freak.distro.conectiva> <3C904437.7080603@candelatech.com> <20020313224255.F9010@work.bitmover.com>
greearb@candelatech.com said:
> I did a clone with this. However, I see no files, only directories.
> The files do seem to be in the SCCS directories, but I don't know how
> to make them appear in their normal place.
Type 'make config'. Make is clever enough to get the Makefile from SCCS for
you. Add the missing dependencies to the Makefile so that make will fetch
stuff like scripts/Configure before trying to run it, etc.
Making it get all the Config.in files by parsing arch/$(ARCH)/config.in is
a fairly trivial task... but you do need to explicitly check out all the
include directories, because we don't know how to deal with that yet. With
kbuild-2.4, make dep won't work very well, but kbuild-2.5 ought to be OK
with everything but the include files, I think.
Or you could just check it all out beforehand with bk -r co.
--
dwmw2
next prev parent reply other threads:[~2002-03-15 11:13 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-14 4:42 Linux 2.4 and BitKeeper Marcelo Tosatti
2002-03-14 6:33 ` Ben Greear
2002-03-14 5:36 ` Marcelo Tosatti
2002-03-14 6:37 ` David S. Miller
2002-03-14 6:42 ` Larry McVoy
2002-03-14 7:54 ` Alex Riesen
2002-03-14 15:46 ` Larry McVoy
2002-03-14 18:10 ` Alex Riesen
2002-03-14 18:19 ` Ben Greear
2002-03-14 18:26 ` Robert Love
2002-03-14 18:40 ` Ben Greear
2002-03-14 22:56 ` Mark Frazer
2002-03-15 11:10 ` David Woodhouse [this message]
2002-03-15 16:04 ` Larry McVoy
2002-03-15 16:17 ` Stelian Pop
2002-03-15 17:58 ` Linus Torvalds
2002-03-15 18:16 ` Jeff Garzik
2002-03-15 18:27 ` Linus Torvalds
2002-03-15 18:47 ` Larry McVoy
2002-03-17 0:39 ` Daniel Phillips
2002-03-17 5:42 ` Mike Fedyk
2002-03-18 16:47 ` [PATCH] 2.5.7-pre2 IDE 22a Martin Dalecki
2002-03-15 18:39 ` Linux 2.4 and BitKeeper Larry McVoy
2002-03-15 19:01 ` Linus Torvalds
2002-03-15 19:10 ` Larry McVoy
2002-03-15 19:20 ` Linus Torvalds
2002-03-15 19:30 ` Larry McVoy
2002-03-16 0:31 ` Andreas Ferber
2002-03-16 1:02 ` Andreas Dilger
2002-03-15 16:10 ` David Woodhouse
2002-03-15 4:35 ` Stephen Torri
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=2865.1016190641@redhat.com \
--to=dwmw2@infradead.org \
--cc=greearb@candelatech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
/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