Nimrod A. Abing wrote:
The graph does not need to be GUI, even text-only will do. I think
something like this can be used to trace how a patch came to be and
will be useful for tracing how a bug (if you're programming) gets
introduced into the repository. If such a tool does not exist, is this
sort of functionality under consideration for future versions?
People have discussed on the list before... Right now it is just a
really tough thing to do. If you want to graph the path a patch has
travelled from repo to repo, you don't have enough information. If you
want to graph the dependencies of a patch, you currently don't have any
way to introspect in darcs to get a reliable look at patch dependencies.
It's one of the same problems that GUIs are up against in trying to
smarter handle darcs pull without just popping up a dialog box for each
darcs question in a mockery of the current interactive way.
--
--Max Battcher--
http://www.worldmaker.net/
"History bleeds for tomorrow / for us to realize and never more follow
blind" --Machinae Supremacy, Deus Ex Machinae, Title Track
_______________________________________________
darcs-users mailing list
[email protected]
http://www.abridgegame.org/mailman/listinfo/darcs-users
