>> Correct. Darcs push is basically
>> darcs send -o - [EMAIL PROTECTED]:dir | ssh [EMAIL PROTECTED] 'cd dir;
>> darcs apply'
> Hm. It would seem you could efficiently avoid that requirement if the
> public repository had no _darcs/current, although you'd need a locking
> protocol.
Running without _darcs/current is already implemented (darcs init
--no-pristine-tree), but you forget the working dir. There's
currently no way to avoid having a working dir in a darcs repo; I
believe there should be one.
David will correct me if I'm wrong, but I believe that in order to
push a patch, you need to read an arbitrary number of remote patches
in order to know what to commute against. While this is not needed in
the simple cases (no reordering of patches necessary), it is done in
more complex cases.
So if you implement --no-working-dir for push, I'll be glad to rename
my proposed new command to
darcs excruciatinglyslowpushbutsortofokayinsimplecases
Juliusz
_______________________________________________
darcs-users mailing list
[email protected]
http://www.abridgegame.org/mailman/listinfo/darcs-users
