Re: RFC - tarball/patch server in BitKeeper

[Ben Collins]

On Mon, Dec 15, 2003 at 03:11:26PM +0300, Sergey Vlasov wrote:
> On Sun, 14 Dec 2003 22:31:04 -0800 Martin J. Bligh wrote:
> 
> > One thing that I've wished for in the past which looks like it *might*
> > be trivial to do is to grab a raw version of the patch you already
> > put out in HTML format, eg if I surf down changesets and get to a page
> > like this:
> > 
> > http://linus.bkbits.net:8080/linux-2.5/patch@xxxxxx?nav=index.html|ChangeSet@-2w|cset@xxxxxx
> > 
> > except it got html formatted, so I can't play with it easily. Is there
> > any way to provide the raw format of that? If not, or you don't want to,
> > no problem - would just be convenient. This isn't a open source vs not
> > issue, it's just I often want one fix without the whole tree, and it'd
> > be a convenient place to grab it.
> 
> You almost can do this now - in most cases, copying the text from
> Mozilla gives a good patch. The only problem is that the HTML
> generation code seems to have a bug - it correctly escapes '<' as
> "&lt;" and '>' as "&gt;", but does not escape '&' as "&amp;", and this
> occasionally leads to problems.
> 
> 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.

You wont be able to get an "XFS changeset".

-- 
Debian     - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
WatchGuard - http://www.watchguard.com/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/