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
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4