Hi fossil users, devs, (I don't remember this idea being discussed, sorry if it has already been proposed.)
The more I have to use git at work, the more I come to appreciate fossil. Yet, companies often have established processes around git'sb quirks and peculiar behavior, making the case for switching to fossil a tough one. Fossil already supports a sort of mutability - by adding branches, appending edits and so on. What if this mechanism is fully extended towards a presentation DAG ? This means keeping the current, history-preserving behavior while allowing for two views into the repository - the raw, as-is and the altered, as-should-be. This allows for example to have a history that is always buildable and testable, therefore making bisects easier. It also allows for a high-level view, where multiple raw commits can be grouped into logical ones for better readability/ I would imagine an implementation where by default the presentation DAG is the same as the raw one and having additional commands (that appear in the raw one as commits) to alter the presentation view. Do you think that this approach is proper and feasible ? Regards, Stanislav Paskalev _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
