On Feb 4, 2008, at 07:28, David Roundy wrote:
> That last post here wasn't actually from me, but from Matt, I just > bounced it to the bug tracker. Anyhow, I agree with him. email > is like motd, it's a repository-specific setting. If I get your > repository, there's no reason why someone sending patches to my > repository should email them to you. > Actually, I agree with everyone that the current behavior is correct (but I have a small suggestion[1]).... Turns out I just did not understand how darcs was looking up the correct email address when doing a "darcs send". To make sure I've go this right.... When doing a "darcs send", darcs retrieves the email address stored in the default repository (most recently pushed or pulled from, without --no-set-default) and then uses that address for the "darcs send". [1] I think what prompted me to misunderstand this to begin with, was that "darcs send -o" does not display the email address that "darcs send" would have used. This forces users who can only "darcs send -o" to manually look up the email address, possibly from a non-standard location in project documentation, which can get out of sync with darcs. IMHO, before "darcs send -o" finishes it should print the email address to which the user is expected to send the patch. Regards, Ben Coburn ---------- status: wont-fix -> chatting title: darcs get does not get email pref -> "darcs send -o" should announce destination email __________________________________ Darcs bug tracker <[EMAIL PROTECTED]> <http://bugs.darcs.net/issue643> __________________________________ _______________________________________________ darcs-devel mailing list darcs-devel@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-devel
