Re: Bitkeeper change granularity (was Re: A modest proposal -- We need a patch penguin)

From: Larry McVoy (lm@bitmover.com)
Date: Sat Feb 02 2002 - 00:50:40 EST

On Fri, Feb 01, 2002 at 07:19:28PM -0600, Charles Cazabon wrote:
> Rob Landley <landley@trommello.org> 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 bitmover.com           http://www.bitmover.com/lm 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

This archive was generated by hypermail 2b29 : Thu Feb 07 2002 - 21:00:20 EST