From: Andrew Thompson <xenuser@aktzero.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: Jim Greer <jbgreer@gmail.com>,
Xen-devel@lists.xensource.com,
"Ronald G. Minnich" <rminnich@lanl.gov>
Subject: Re: Xen repository
Date: Mon, 23 May 2005 09:06:56 -0400 [thread overview]
Message-ID: <4291D570.6040909@aktzero.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D1E4173@liverpoolst.ad.cl.cam.ac.uk>
Ian Pratt wrote:
> BK's algorithm for slecting the main branch is very 'odd' indeed, and as
> it stands we'd loose a great deal of the revision history. I reckon we
> could do a much better job of linearizing the history (possibly with a
> bit of manual intervention).
I'm not really familiar with bitkeeper or this pick-your-patches style
of management/merging. Is there useful documentation outside of the
bigkeeper user guide? (googling bitkeeper gives two pages of bitkeeper
vs linux/open source hits)
> Can anyone think of a way of getting
> bitkeeper to output the revision DAG in a parseable form? Having this
> would also make it possible to keep the branch structure while
> transfering to a tool like mercurial or cogito.
I'm not sure what DAG is, but I read a lkml posting from Linus that
stated he had scripted a method of dumping data from BitKeeper, but
hadn't used it because he expected it to take days to complete(to pull
the kernel source tree).
--
Andrew Thompson
http://aktzero.com/
next prev parent reply other threads:[~2005-05-23 13:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-23 7:47 Xen repository Ian Pratt
2005-05-23 8:27 ` aq
2005-05-23 15:17 ` Ronald G. Minnich
2005-05-23 13:06 ` Andrew Thompson [this message]
2005-05-23 16:38 ` Arun Sharma
2005-05-25 8:42 ` Nicholas Lee
2005-05-25 17:26 ` Arun Sharma
2005-05-25 17:35 ` Roland Dreier
2005-05-25 18:00 ` Ronald G. Minnich
2005-05-23 21:25 ` Jacob Gorm Hansen
-- strict thread matches above, loose matches on Subject: below --
2005-05-23 9:11 Ian Pratt
2005-05-24 19:21 ` Paul Larson
2005-05-24 19:55 ` Ronald G. Minnich
2005-05-21 20:16 Ian Pratt
2005-05-21 19:52 ` Mark Williamson
2005-05-22 1:00 ` Rik van Riel
2005-05-23 9:47 ` Vincent Hanquez
2005-05-22 2:42 ` aq
2005-05-23 3:34 ` Ronald G. Minnich
2005-05-21 16:28 Nakajima, Jun
2005-05-21 16:24 Jim Greer
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=4291D570.6040909@aktzero.com \
--to=xenuser@aktzero.com \
--cc=Xen-devel@lists.xensource.com \
--cc=jbgreer@gmail.com \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=rminnich@lanl.gov \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.