Trent W. Buck wrote:
This allows some interesting workflows. For example: a patch can only
go in the stable branch if it's signed by a core developer.
I realize you're not a fan of "darcs send", but the user manual
describes such a workflow using signed patch bundles via email, applied
automatically with procmail.
1. Indeed, not everybody likes darcs send. I don't understand why you
keep pushing it. Darcs send is just your personal preference and you
shouldn't require other people to work the way you like to work before
they can get some security.
2. You already know that darcs send doesn't address the use cases I'm
interested in. When I download the latest copy of Darcs, I am not using
darcs send.
Daniel.
_______________________________________________
darcs-users mailing list
[email protected]
http://lists.osuosl.org/mailman/listinfo/darcs-users
