mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: rmoser <mlmoser@comcast.net>
To: Larry McVoy <lm@bitmover.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel source tree splitting
Date: Wed, 30 Apr 2003 21:00:30 -0400	[thread overview]
Message-ID: <200304302100300700.0157A42C@smtp.comcast.net> (raw)
In-Reply-To: <20030501005224.GA8676@work.bitmover.com>



*********** REPLY SEPARATOR  ***********

On 4/30/2003 at 5:52 PM Larry McVoy wrote:

>It would be *really* cool if the Makefile dependencies actually worked.
>It's a very little known fact but if you are in an RCS or SCCS (and BK
>looks like SCCS to make) source tree and the files are not checked out,
>you can just say
>
>	make
>
>and make will look for a makefile, if there isn't one but there is a
>SCCS/s.[Mm]akefile it will check it out, look at the dependencies and start
>checking those out and keep doing it to satisfy the target.
>
>It's a really pleasant way to work, the "make clobber" target "cleans"
>all the source so it isn't checked out, the directory is nice and empty.
>This makes it easy to see stuff you still need to check in or think about.
>It's definitely an old timer way of working, I'm pretty sure that the
>original Unix was done this way but just because it is old doesn't mean
>it is bad.  Opinions differ on that :)
>
>Here's a make in a cleaned BK source tree:
[cut]

....

Larry... what the heck are you talking about?  No really you lost me
:)

Are you talking about hitting a button and flushing all the code but
what's new, or about actually making different tarballs cause the
source tree to auto-adapt to what's in it?

What is RCS/SCCS

--Bluefox Icy


  reply	other threads:[~2003-05-01  0:49 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 [this message]
2003-05-01 17:28     ` James H. Cloos Jr.
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=200304302100300700.0157A42C@smtp.comcast.net \
    --to=mlmoser@comcast.net \
    --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

all inboxes | Powered by JetHome®