Comments on: Patch-Tag is now darcs send friendly for mailing patches to repo owner http://blog.patch-tag.com/2009/10/14/patch-tag-is-now-darcs-send-friendly/ give your code a home Fri, 13 Jul 2012 17:30:25 +0000 hourly 1 http://wordpress.com/ By: kowey http://blog.patch-tag.com/2009/10/14/patch-tag-is-now-darcs-send-friendly/#comment-63 Mon, 19 Oct 2009 12:57:42 +0000 http://blog.patch-tag.com/?p=204#comment-63 Looks good :-)

]]> By: thomashartman1 http://blog.patch-tag.com/2009/10/14/patch-tag-is-now-darcs-send-friendly/#comment-62 Fri, 16 Oct 2009 21:24:26 +0000 http://blog.patch-tag.com/?p=204#comment-62 Hey Eric, thanks for pointing out the typos and making the wording suggestsions.

Did as you suggested, and having a look at the email override feature.

]]> By: Magnus http://blog.patch-tag.com/2009/10/14/patch-tag-is-now-darcs-send-friendly/#comment-61 Fri, 16 Oct 2009 09:28:32 +0000 http://blog.patch-tag.com/?p=204#comment-61 Thanks for adding this!

]]> By: kowey http://blog.patch-tag.com/2009/10/14/patch-tag-is-now-darcs-send-friendly/#comment-59 Thu, 15 Oct 2009 10:52:14 +0000 http://blog.patch-tag.com/?p=204#comment-59 Yay! Note that the instructions have a couple of typos: abot; dont’; prjoect.

I would avoid calling it “pushing over email” because pushing implies that the patches actually get applied in the remote repository. “Sending over email” is probably a more accurate formulation.

Also, you can use the -O flag to avoid choosing a name for the patch bundle (darcs send -O will create a patch bundle using the same sort of name as it would have created for its attachments).

Finally, one use case to think about in the future may be projects (such as Darcs and xmonad) whose workflow involves sending patches to a mailing list; or similarly users who want to use separate email addresses for separate projects. So perhaps in the future it would make sense to be able to override the default email with one you supply over a text box (presumably with some sort of sanitisation)

]]>