Hello, I was looking for a way how to realize workflow with small development commits without cluttering the history at the same time.
Some git users squash such development commits into a single one when a particular feature is finished. While this makes the history much clearer, a lot of important information is lost. (Moreover this method is a bit error prone, because such squashing must be done before pushing changes into a remote repository.) Ideally, one wants to have a clean history and at the same time some kind of access to the original detailed commits. (See also my SO question: Should I squash small, development commits into bigger ones? http://stackoverflow.com/q/14554110/1333025) Recently I've been told that mercurial is working on a concept that allows to safely "rewrite" history. As I understand it, it actually doesn't modify anything, it just adds specific information (markers) that signals that some commits should be invisible or visually replaced by something else. These markers are propagated between repositories just as other stuff so working with them is fully distributed and the history of what has been done is preserved. See http://mercurial.selenic.com/wiki/ChangesetEvolution I wonder, would it be possible/difficult to add something like that to darcs? Best regards, Petr Pudlak
_______________________________________________ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
