Greg Ewing greg.ewing at canterbury.ac.nz
Tue Mar 22 00:46:22 CET 2011

• Previous message: [Python-Dev] Hg: inter-branch workflow
• Next message: [Python-Dev] Hg: inter-branch workflow
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

Ben Finney wrote:

> That seems to me the ideal: preserve all revision history for those
> cases when some user will care about it, but *present* history cleanly
> by default.

Seems to me the basic problem here is the way Mercurial
presents you with a big pile of changesets and not much
way of imposing any structure on them.

There should be a hierarchy of changesets, so you can
look at the top level and get the big picture, while
being able to drill down into the details when you
need to.

-- 
Greg

---

• Previous message: [Python-Dev] Hg: inter-branch workflow
• Next message: [Python-Dev] Hg: inter-branch workflow
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list