Thinking more about it I came to the conclusion that this is not actually
a push variant rather a 'darcs mirror', since selective pushes might mean
an inconsistent remote repo, since skipping the apply step means skipping
validity check. But for a darcs mirror operation I think it would be
just OK.
Actually, I think darcs is sufficiently well bug-tested that I wouldn't
worry about the consistency checking. Leaving out the working directory
I was under the impression that unless a patch application is tried to a working copy
there is no way of finding out if the resulting repo is consistent. Using manual copying
of patches under _darcs of a remote could lead to a situation where the repo gets
inconsistent. But I suppose that with darcs push, the client darcs wouldn't let you push
patches unless their dependencies were pushed as well so I guess you're right.
would be quite a reasonable feature to add, and would actually make the
apply code significantly faster in comparison with --no-pristine. It just
takes someone who wants to put in the effort to support this.
What is the new interface/option you have in mind? Adding a --no-working-dir option to
apply? I'll try doing it one of the following weekends unless someone else steps up.
Jani
_______________________________________________
darcs-users mailing list
[email protected]
http://www.abridgegame.org/mailman/listinfo/darcs-users
