[EMAIL PROTECTED] wrote:
My impression (and I don't
presume to have any weight around here, granted) is that this is way too
specific a thing to get into the darcs code.
For what it is worth, I currently accomplish something similar just by pulling
all of the patches of a dozen different projects into one repo, and remembering
not to create patches that touch multiple sub-projects at once.
Maybe all that is really needed is some user interface niceties for the
scenarios where you create multiple nested darcs repositories. Such as
warnings when patches might span repositories (or even some option to
allow darcs to "automagically" split such patches into individual
per-repo patches).
--
--Max Battcher--
http://www.worldmaker.net/
_______________________________________________
darcs-users mailing list
[email protected]
http://www.abridgegame.org/mailman/listinfo/darcs-users
