On Sun, Nov 30, 2008 at 16:19:44 -0500, Gwern Branwen wrote: > One thing I like about the idea of setprefing email is that, aside > from a more consistent UI, it makes forking clearer; the new person > does a 'darcs setpref email [EMAIL PROTECTED] && darcs replace jhc lhc > `find .` && darcs replace old-address new-address `find .`'* and he's > basically done everything needed to change the name, address, and > where patches go. Or if it's not a fork but some sort of branch, a > developer who has fetched that branch, she can set the email to the > main branch and every so often fire off a bundle. And so on.
Well, my position on this is probably on the patches welcome side. It would be good if the person writing such a patch could work out a sensible plan for (a) interacting with the local email pref and (b) working with older versions of darcs Thanks! -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9
pgpkfsK6cWovL.pgp
Description: PGP signature
_______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
