[lkml]   [2002]   [Feb]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Bitkeeper change granularity (was Re: A modest proposal -- We need a patch penguin)
On Fri, Feb 01, 2002 at 07:19:28PM -0600, Charles Cazabon wrote:
> Rob Landley <> wrote:
> >
> > The problem is, if they use bitkeeper (with a temporary respository), all
> > these temporary commits (debugging tries saved in case they want to roll back
> > during development) get propagated into the main repository when they do a
> > merge. They can't tell it "done, okay, squash this into one atomic change to
> > check in somewhere else, with the whole change history as maybe one comment".
> Something like:
> bk start-temporary-fork

bk clone main temporary-fork

> [hack hack hack]
> bk commit
> [hack hack hack]
> bk revert

bk fix -c

> [hack hack hack]
> bk commit
> [hack hack hack]
> bk commit
> bk fold-back-into-main-tree-as-one-atomic-update

bk push

All exists, works as described, no changes necessary.
Larry McVoy lm at
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:23    [W:0.263 / U:0.608 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site