Miklos Vajna <[email protected]> writes:
> I think the problem is that you can push a setpref patch, then a
> simple 'darcs apply' will fire you as well. That's why - because of
> the security problem, by design - for example git does not allow you
> to push such 'setpref' patches at all.
I've always been annoyed by the seemingly arbitrary distinction in Darcs
between repo settings that propagate (such as the test command) and ones
you can't (such as the motd and author). The reason I never set author
correctly is because I always forget to re-create it after branching...
I wonder if you can trivially prevent application of setpref patches by
making it inaccessible to Darcs, e.g.
chmod 1755 _darcs/prefs
chmod 0 _darcs/prefs/prefs
sudo chown root:root _darcs/prefs/prefs
_______________________________________________
darcs-users mailing list
[email protected]
http://lists.osuosl.org/mailman/listinfo/darcs-users
