[Python-Dev] Mercurial workflow question... (original) (raw)
Stephen J. Turnbull stephen at xemacs.org
Fri Dec 14 08:14:29 CET 2012
- Previous message: [Python-Dev] Mercurial workflow question...
- Next message: [Python-Dev] Mercurial workflow question...
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
R. David Murray writes:
those commits...if you don't want those intermediate commits in the official repo, then why is a diff/patch a bad way to achieve that?
Because a decent VCS provides TOOWTDI. And sometimes there are different degrees of "intermediate", or pehaps you even want to slice, dice, and mince the patches at the hunk level. Presenting the logic of the change often is best done in pieces but in an ahistorical way, but debugging often benefits from the context of an exact sequential history.
That said, diff/patch across repos is not per se evil, and may be easier for users to visualize than the results of the DAG transformations (such as rebase) provided by existing dVCSes.
- Previous message: [Python-Dev] Mercurial workflow question...
- Next message: [Python-Dev] Mercurial workflow question...
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]