Eric Kow wrote:
Don't take this too too seriously by the way; it really is just random
grumpiness.
I just feel more comfortable with the idea of being able to look at a
context file and tell at a glance what it's doing (in the same way that
old-fashioned pristine for its many shortcomings is more convenient).
I was thinking about this a little bit, too, Eric. Particularly if a
two-hash context format "infected" the contexts of patch bundles, there
are many times in reviewing patches sent to the mailing list where it
can be useful to get some "at-a-glance" information on roughly what sort
of repository/branch the sender was working in... Some of that will
still be apparent in the size and patterns in even a two-hash context.
(On the plus side it might be nice for mailing lists in general just to
drop the average patch bundle size.)
What might work is simply darcs changes support for contexts, something
like:
darcs changes --of-context some.context
A key benefit here is also that you get a visual way to inspect when
darcs cannot locate a patch at all, before you attempt to rely on it in
a get/apply/send. Darcs changes could even provide some sort of
assistance at this point on how to request a copy of the necessary
patch(es) from the repository that the context is related to.
--
--Max Battcher--
http://worldmaker.net
_______________________________________________
darcs-users mailing list
[email protected]
http://lists.osuosl.org/mailman/listinfo/darcs-users
