On Sat, Nov 25, 2006 at 10:30:33AM -0500, Sean wrote:
If your mail setup support imap, the patches can be dumped directly into
it rather than having to go through an mbox. For instance you can have
something like this in your ~/.gitconfig:
Sure, I could. But if you have a client which supports mboxes, it's
probably better to use the mbox. With your solution, I send the patch to
the imap server, then fire up the mail client and re-download the
patch, possibly mark it up, and then send it out by smtp. The latency
increase can be noticeable, especially for big patches and slow imap
servers.
To move all the patches into your imap drafts folder to be accessed
by whatever email client you use.
Oh come on, Real Men just edit the mbox in vi. :)
On Sat, 25 Nov 2006 10:39:49 -0500
Jeff King [off-list ref] wrote:
On Sat, Nov 25, 2006 at 10:30:33AM -0500, Sean wrote:
quoted
If your mail setup support imap, the patches can be dumped directly into
it rather than having to go through an mbox. For instance you can have
something like this in your ~/.gitconfig:
Sure, I could. But if you have a client which supports mboxes, it's
probably better to use the mbox. With your solution, I send the patch to
the imap server, then fire up the mail client and re-download the
patch, possibly mark it up, and then send it out by smtp. The latency
increase can be noticeable, especially for big patches and slow imap
servers.
Yeah, I didn't mean it as a better replacement for your use, just as
an option that might suit some people better. It works out well here.
quoted
To move all the patches into your imap drafts folder to be accessed
by whatever email client you use.
Oh come on, Real Men just edit the mbox in vi. :)
Damn.. caught in my skirt again.. ;o)