mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Larry McVoy <lm@bitmover.com>
Cc: Willy TARREAU <willy@w.ods.org>,
	Chuck Ebbert <76306.1226@compuserve.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Kernel source tree splitting
Date: Thu, 01 May 2003 08:11:32 -0700	[thread overview]
Message-ID: <16100000.1051801891@[10.10.2.4]> (raw)
In-Reply-To: <20030501150110.GA13282@work.bitmover.com>

>> -r--r--r--  1689 fletch   fletch      18691 Nov 17 20:29 COPYING
> 
> That's a bunch.  Who's fletch?  
> 
> And more importantly, how do you keep track of what is in each of those?
> I can see having 20, 100, whatever, and keeping it straight in your head
> but 1600?  

I have one view for every patch, and a bunch of scripts to manage them,
tear them down, build them up, and create patches from all of them in one
dir (they're a numbered sequence). A decent tree structure helps ;-)

It helps me to keep all the patches separated out - I want to be able to
carry forward 100 patches (at least) in sequence against the mainline tree,
and keep them all separate. Totally different problem from the one Linus
has, IMHO. 

I guess I have a view for what you call a changeset ... AFAICS, if you just
take 100 stacked patches, and do a merge forward through 30 versions, you
just end up with a big mess that you can't extract the real "changes"
you're making back out from the main view. But I've never really tried, it
might work out in BK or something I suppose. If that worked (in ~1 minute
for 100 patches), I'd be very tempted to try it (I hate learning curves for
new tools, half the time they're just burnt time).

> We'll still never be as fast as a pure hardlinked tree, that's balls to
> the wall as fast as you can go as far as I can tell.

Ow ;-)

M.


  reply	other threads:[~2003-05-01 14:59 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2003-05-01 17:22 ` Balram Adlakha
2003-05-01 17:28   ` Ben Greear
2003-05-01 20:03     ` John Bradford
  -- strict thread matches above, loose matches on Subject: below --
2003-05-01 16:00 Chuck Ebbert
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.
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

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='16100000.1051801891@[10.10.2.4]' \
    --to=mbligh@aracnet.com \
    --cc=76306.1226@compuserve.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@bitmover.com \
    --cc=willy@w.ods.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®