> One way to look at it is that "darcs changes" is showing you the
> history of how your local repo changed. If today you pull a patch
> P1 that was written in 2005, and tomorrow you pull a patch P2 that
> was written in 2004, then running "darcs changes" will help you
> remember that there was a time when you had P1 but not P2, and then
> a later time when you had both.
This is correct, and this is without doubt the way |darcs changes|
should behave when given no arguments.
On the other hand, it should be possible to ask |darcs changes| to
sort the patch chronologically up to patch dependence.
(To be more precise, sorted according the total order O compatible with
the dependence relation such that O intersected with chronological
order is maximal among the set of such things.)
Why the plain old chronological ordering is not necessarily compatible
with patch dependence is left as an exercice for the reader.
Juliusz
_______________________________________________
darcs-users mailing list
[email protected]
http://www.abridgegame.org/mailman/listinfo/darcs-users
