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

Charles Cazabon
2002-02-02T01:20:17Z

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
[hack hack hack]
bk commit
[hack hack hack]
bk revert
[hack hack hack]
bk commit
[hack hack hack]
bk commit
bk fold-back-into-main-tree-as-one-atomic-update

?

Charles
--
-----------------------------------------------------------------------
Charles Cazabon <linux@discworld.dyndns.org>
GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/
-----------------------------------------------------------------------