On Monday, August 19, 2013 13:09:54 Tor Arntsen wrote:
> On 19 August 2013 12:44, Steve Holme <steve_holme_at_hotmail.com> wrote:
> > Additionally, is there any possibility you could attach your .patch files
> > rather than sending them as separate emails?
> >
> > This way we don't have to try and compare emails with code and don't have
> > to try and save emails as .patch files where we can get the line endings
> > wrong or even incorrect line wrappings - From my own perspective I can
> > then use the built in review features of TortoiseGIT's ;-)
>
> Those patch emails didn't have any line-ending / wrapping issues and
> should apply without problem (if wrapping etc. happens or not
> generally depends on the sending end and not the receiving end, and
> I've used a specifically configured Thunderbird for this in the past
> with no problems. When I send from gmail though it doesn't work well).

Those patches look like they were sent by git send-email, which is the most
reliable tool for sending git patches in my experience. Nothing against
Thunderbird, or Google's web UI of course :-)

> I like to see the diff in the email itself, it's very easy to follow
> and review the set of patches that way. The Git mailing list way..
> great for review and testing.
> On the other hand I myself tend to add the patch as an attachment as
> well, thus getting the best of both worlds.

I would expect any useful e-mail client to have the ability of saving e-mails
as text files. Are there any e-mail clients around that know how to save text
attachments, but not the e-mail itself?

Kamil
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2013-08-19