Re: Changelogs on kernel.org

[Larry McVoy <lm@bitmover.com>]

On Wed, May 15, 2002 at 09:03:40PM +0100, David Woodhouse wrote:
> 
> lm@bitmover.com said:
> > FYI, if they do a 
> > 	bk send -ubk://linux.bkbits.net/linux-2.5 torvalds@transmeta.com
> > that problem goes away.  The -u<url> stuff does the same sort of
> > handshake that a pull does to figure out what needs to be sent to fill
> > in the holes.
> 
> Not quite. The sender usually omits changesets for a _reason_. You'll often
> find that one of the changesets in the middle wasn't necessary and didn't
> touch any of the same files -- in which case patches would have applied 
> just fine.

Understood.  BK doesn't work that way for multiple reasons, some which have
to do with how it synchronizes replicas, and some which have to do with
being able to reproduce a tree exactly.

It's probably best if you simply view this as a BK limitation which isn't
going away any time soon and don't put junk changesets in the middle of
your stream of changes.  It's easy enough to export the change you want
as a patch, export the comments in the form that bk comments wants,
undo the junk changeset, import the patch, and set the comments.  Yeah,
it's awkward; consider that a feedback loop which encourages you to
think a bit more about what you put in the tree.
-- 
---
Larry McVoy            	 lm at bitmover.com           http://www.bitmover.com/lm