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/ ----------------------------------------------------------------------- - 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