From: Larry McVoy <lm@bitmover.com>
To: David Lang <david.lang@digitalinsight.com>,
Larry McVoy <lm@bitmover.com>,
Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>,
linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] BK->CVS (real time mirror)
Date: Sat, 15 Mar 2003 08:52:29 -0800 [thread overview]
Message-ID: <20030315165229.GA23205@work.bitmover.com> (raw)
In-Reply-To: <20030312161813.S12806@schatzie.adilger.int>
> > I suspect the right answer is that we do the real time updates, see how it
> > goes, if it starts to suck we'll periodically toss the CVS tree and start
> > over.
>
> What you could do is have a CVS "realtime" branch which is forked from the
> trunk, say once a week, or whenever Linux makes a point release.
I'm not sure it is worth it. If you are using BK, run revtool and look at
the recent history in 2.5. I just updated the CVS tree on kernel.bkbits.net
and looked carefully at the collapsing it did. It collapsed a pile of Greg's
stuff into one cset, but that's actually OK as far as I can tell, it's all
related. And there was more work on the other path.
We've done several updates to the 2.5 tree and so far the number of changesets
we would have gotten if we had done it all in one pass and the number that
we actually got is identical. So maybe the reality of the incremental updates
is better than we expected.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2003-03-15 16:41 UTC|newest]
Thread overview: 109+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-12 17:42 [ANNOUNCE] BK->CVS (real time mirror) Larry McVoy
2003-03-12 18:01 ` Roman Zippel
2003-03-12 18:34 ` Ben Collins
2003-03-12 19:03 ` Sam Ravnborg
2003-03-12 19:38 ` Roman Zippel
2003-03-12 19:32 ` Nicolas Pitre
2003-03-12 19:53 ` Ben Collins
2003-03-12 20:09 ` Ben Collins
2003-03-12 20:20 ` Jeff Garzik
2003-03-12 23:58 ` Roman Zippel
2003-03-12 20:37 ` Nicolas Pitre
2003-03-13 2:57 ` Aaron Lehmann
2003-03-16 3:48 ` Andrea Arcangeli
2003-03-16 17:45 ` Roman Zippel
2003-03-16 18:54 ` Nicolas Pitre
2003-03-16 19:30 ` Shawn
2003-03-16 19:33 ` Roman Zippel
2003-03-16 21:52 ` Andrea Arcangeli
2003-03-17 1:18 ` Roman Zippel
2003-03-17 1:35 ` Larry McVoy
2003-03-17 1:56 ` Roman Zippel
2003-03-17 9:01 ` Henning P. Schmiedehausen
2003-03-17 17:46 ` Daniel Phillips
2003-03-17 18:04 ` Jeff Garzik
2003-03-17 19:32 ` Jamie Lokier
2003-03-17 19:40 ` David Lang
2003-03-17 20:00 ` Jamie Lokier
2003-03-17 20:43 ` Andrea Arcangeli
2003-03-17 20:12 ` Roman Zippel
2003-03-17 21:56 ` Pavel Machek
2003-03-17 22:08 ` Andrea Arcangeli
2003-03-21 14:16 ` Larry McVoy
2003-03-21 17:42 ` Andrea Arcangeli
2003-03-21 19:40 ` H. Peter Anvin
2003-03-22 0:15 ` Larry McVoy
2003-03-22 0:51 ` H. Peter Anvin
2003-03-17 17:41 ` Horst von Brand
2003-03-17 18:04 ` Petr Baudis
2003-03-12 19:21 ` Nicolas Pitre
2003-03-12 19:51 ` Larry McVoy
2003-03-12 20:08 ` Ben Collins
2003-03-12 20:14 ` Sam Ravnborg
2003-03-12 20:18 ` Larry McVoy
2003-03-12 20:46 ` Nicolas Pitre
2003-03-12 20:58 ` Larry McVoy
2003-03-12 21:08 ` Nicolas Pitre
2003-03-13 0:41 ` Larry McVoy
2003-03-12 21:18 ` Eli Carter
2003-03-13 20:45 ` Horst von Brand
2003-03-13 1:58 ` Larry McVoy
2003-03-13 23:40 ` Larry McVoy
2003-03-12 21:05 ` Daniel Jacobowitz
2003-03-12 21:18 ` Larry McVoy
2003-03-12 21:31 ` Daniel Jacobowitz
2003-03-12 21:33 ` Larry McVoy
2003-03-12 21:45 ` Kai Germaschewski
2003-03-12 22:01 ` Larry McVoy
2003-03-12 22:21 ` David Lang
2003-03-12 22:30 ` Larry McVoy
2003-03-12 23:18 ` Andreas Dilger
2003-03-15 16:52 ` Larry McVoy [this message]
2003-03-13 21:00 ` Horst von Brand
2003-03-13 9:43 ` Geert Uytterhoeven
2003-03-13 23:26 ` Larry McVoy
2003-03-14 8:53 ` Geert Uytterhoeven
-- strict thread matches above, loose matches on Subject: below --
2003-03-17 23:08 David Mansfield
2003-03-17 23:25 ` Andrea Arcangeli
2003-03-17 23:33 ` Larry McVoy
2003-03-17 23:57 ` Andrea Arcangeli
2003-03-18 1:48 ` David Mansfield
2003-03-18 2:43 ` Andrea Arcangeli
2003-03-13 15:38 David Mansfield
2003-03-13 15:42 ` Larry McVoy
2003-03-12 3:43 Larry McVoy
2003-03-12 4:16 ` Ben Collins
2003-03-12 8:55 ` Jens Axboe
2003-03-12 10:26 ` Andreas Dilger
2003-03-12 10:31 ` Jens Axboe
2003-03-12 10:56 ` Andreas Dilger
2003-03-12 11:15 ` Jens Axboe
2003-03-12 11:20 ` Jamie Lokier
2003-03-12 16:13 ` H. Peter Anvin
2003-03-12 16:30 ` Dana Lacoste
2003-03-12 16:47 ` John Bradford
2003-03-12 17:08 ` Roman Zippel
2003-03-12 21:50 ` Alan Cox
2003-03-13 23:30 ` Roman Zippel
2003-03-12 17:29 ` H. Peter Anvin
2003-03-12 17:57 ` John Bradford
2003-03-12 18:03 ` Larry McVoy
2003-03-12 20:49 ` H. Peter Anvin
2003-03-13 7:59 ` Theodore Ts'o
2003-03-13 9:58 ` Roman Zippel
2003-03-12 16:18 ` Ben Collins
2003-03-12 16:47 ` Lars Marowsky-Bree
2003-03-12 17:34 ` Ryan Anderson
2003-03-12 18:38 ` Arador
2003-03-12 18:47 ` Ben Collins
2003-03-12 19:12 ` Andreas Dilger
2003-03-13 0:29 ` Martin J. Bligh
2003-03-13 0:56 ` Larry McVoy
2003-03-16 3:44 ` Andrea Arcangeli
2003-03-12 4:39 ` H. Peter Anvin
2003-03-12 4:56 ` Larry McVoy
2003-03-16 3:10 ` Andrea Arcangeli
2003-03-12 19:34 ` Brandon Low
2003-03-16 13:45 ` Pavel Machek
2003-03-17 14:18 ` Wayne Scott
2003-03-17 14:45 ` Pavel Machek
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=20030315165229.GA23205@work.bitmover.com \
--to=lm@bitmover.com \
--cc=david.lang@digitalinsight.com \
--cc=kai@tp1.ruhr-uni-bochum.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox