From: "James H. Cloos Jr." <cloos@jhcloos.com>
To: Larry McVoy <lm@bitmover.com>
Cc: "Randy.Dunlap" <rddunlap@osdl.org>, rmoser <mlmoser@comcast.net>,
linux-kernel@vger.kernel.org
Subject: Re: Kernel source tree splitting
Date: 01 May 2003 13:28:16 -0400 [thread overview]
Message-ID: <m3n0i6zidr.fsf@lugabout.jhcloos.org> (raw)
In-Reply-To: <20030501005224.GA8676@work.bitmover.com>
>>>>> "Larry" == Larry McVoy <lm@bitmover.com> writes:
Larry> It's a very little known fact but if you are in an RCS
Larry> or SCCS (and BK looks like SCCS to make) source tree and the
Larry> files are not checked out, you can just say
Larry> make
Larry> and make will look for a makefile, if there isn't one but there
Larry> is a SCCS/s.[Mm]akefile it will check it out, look at the
Larry> dependencies and start checking those out and keep doing it to
Larry> satisfy the target.
That has never worked for me with Linus' or Marcello's trees. It
always falls down at some point or other.
Usually it fails looking for something under include, 2.5 also dies
in make oldconfig.
-JimC
next prev parent reply other threads:[~2003-05-01 17:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-30 23:46 rmoser
2003-05-01 0:21 ` Randy.Dunlap
2003-05-01 0:44 ` rmoser
2003-05-01 2:51 ` Randy.Dunlap
2003-05-01 10:13 ` rmoser
2003-05-01 0:52 ` Larry McVoy
2003-05-01 1:00 ` rmoser
2003-05-01 17:28 ` James H. Cloos Jr. [this message]
2003-05-01 4:10 ` Martin J. Bligh
2003-05-01 6:14 ` Ed Sweetman
2003-05-01 6:14 ` Peter Riocreux
2003-05-02 0:09 ` Randy.Dunlap
2003-05-02 0:41 ` rmoser
2003-05-01 11:54 Chuck Ebbert
2003-05-01 14:06 ` Martin J. Bligh
2003-05-01 14:20 ` Willy TARREAU
2003-05-01 14:35 ` Martin J. Bligh
2003-05-01 14:43 ` Willy TARREAU
2003-05-01 15:01 ` Larry McVoy
2003-05-01 15:11 ` Martin J. Bligh
2003-05-01 17:22 ` Balram Adlakha
2003-05-01 17:28 ` Ben Greear
2003-05-01 20:03 ` John Bradford
2003-05-01 16:00 Chuck Ebbert
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=m3n0i6zidr.fsf@lugabout.jhcloos.org \
--to=cloos@jhcloos.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
--cc=mlmoser@comcast.net \
--cc=rddunlap@osdl.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®