From: Sergey Vlasov <vsu@altlinux.ru>
To: linux-kernel@vger.kernel.org
Cc: bitkeeper-users@bitmover.com
Subject: Re: RFC - tarball/patch server in BitKeeper
Date: Mon, 15 Dec 2003 19:24:02 +0300 [thread overview]
Message-ID: <20031215192402.528ce066.vsu@altlinux.ru> (raw)
In-Reply-To: 20031215132720.GX7308@phunnypharm.org
On Mon, 15 Dec 2003 08:27:20 -0500 Ben Collins wrote:
> On Mon, Dec 15, 2003 at 03:11:26PM +0300, Sergey Vlasov wrote:
> > I see another missing feature - there does not seem to be a way to
> > order the changesets by the order of merging them into the tree. E.g.
> > when you look at the linux-2.4 changesets, you will now find XFS all
> > over the place - even before 2.4.23, while it really has been merged
> > after 2.4.23.
>
> You don't seem to understand how bitkeeper works then. Back when the XFS
> tree was cloned from the 2.4 tree, it began it's own "branch". Over time
> it has merged code from the 2.4 tree, and it's work has occured over
> this same time.
>
> When XFS was merged back into the 2.4 tree, it retains all of that
> history in sort of a split road looking branch/merge.
Keeping that history is good. But the main 2.4 branch also has its own
history - and it shows that there were no XFS code in that branch up
to and including 2.4.23.
There does not seem to be a way to get this information - at least
through bkbits.net.
next prev parent reply other threads:[~2003-12-15 16:24 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-14 17:21 RFC - tarball/patch server in BitKeeper Larry McVoy
2003-12-14 23:05 ` Keith Owens
2003-12-14 23:44 ` Larry McVoy
2003-12-15 0:25 ` Keith Owens
2003-12-15 3:47 ` Larry McVoy
2003-12-14 23:17 ` Tupshin Harper
2003-12-14 23:43 ` Larry McVoy
2003-12-15 0:19 ` Tupshin Harper
2003-12-15 3:46 ` Larry McVoy
2003-12-15 6:07 ` Tupshin Harper
2003-12-15 16:02 ` Larry McVoy
2003-12-15 19:52 ` Tupshin Harper
2003-12-15 6:31 ` Martin J. Bligh
2003-12-15 12:11 ` Sergey Vlasov
2003-12-15 13:27 ` Ben Collins
2003-12-15 16:24 ` Sergey Vlasov [this message]
2003-12-15 16:32 ` Larry McVoy
2003-12-15 18:31 ` Andrea Arcangeli
2003-12-15 18:58 ` Larry McVoy
2003-12-15 19:40 ` Andrea Arcangeli
2003-12-15 21:44 ` Larry McVoy
2003-12-15 22:02 ` Andrea Arcangeli
2003-12-15 22:14 ` Larry McVoy
2003-12-15 22:44 ` Tupshin Harper
2003-12-15 23:13 ` Andrea Arcangeli
2003-12-15 22:36 ` Tupshin Harper
2003-12-15 22:46 ` Larry McVoy
2003-12-15 23:08 ` Tupshin Harper
2003-12-17 4:47 ` Matthew D. Pitts
2003-12-15 15:42 ` Larry McVoy
2003-12-15 15:55 ` Martin J. Bligh
2003-12-15 23:18 ` Chris Frey
2003-12-21 20:02 ` Pavel Machek
2003-12-21 20:46 ` John Bradford
2003-12-24 1:49 ` Larry McVoy
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=20031215192402.528ce066.vsu@altlinux.ru \
--to=vsu@altlinux.ru \
--cc=bitkeeper-users@bitmover.com \
--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 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.