Re: FEATURE REQUEST: git-format-path: Add option to encode patch content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Johannes Schindelin <Johannes.Schindelin@xxxxxx> writes:

> Hi,
>
> On Fri, 27 Apr 2007, Jari Aalto wrote:
>
>> FEAURE REQUEST
>> --------------
>> 
>> Add sme option to git-format-path to encode thae patch content 
>> (MIME/base64)
>
> Although you ask politely, and have a good explanation why you need it, 
> there is a strong sentiment in some Git developers (most notably, Git's 
> inventor) against this kind of support.
>
> You might have more luck when you decide to implement it yourself, and 
> submit it, though (if it is not too intrusive, I see people adding it, if 
> only to add even more rope to those willing to hang themselves).
>
> Having said that, I think that you can actually teach every mail app 
> (except maybe web-based ones) to respect formatting, including white 
> space.

I hope the development team considers this. There is another uses case
that I can think of too:

- Sending non us-ascii patches (different langauge)

For documentation or code (Java/XML allows UTF-8). 

Jari

-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]