Re: FEATURE REQUEST: git-format-path: Add option to encode patch content
- From
Jari Aalto <jari.aalto@cante.net>
- Date
- Apr 27, 2007, 17:33 UTC
- Message-ID
- <d51pzpqo.fsf@cante.net>
- In-Reply-To
- <Pine.LNX.4.64.0704271541010.12006@racer.site>
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
Show 21 quoted lines
> 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