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

FEAURE REQUEST
--------------

Add sme option to git-format-path to encode thae patch content 
(MIME/base64)

RATIONALE
-------------

I need to submit patches that fix trailing whitespcaes, and to guard
those in email message it would be nice if the patch could be made
into base64 envelope (or MIME)

-- Jari

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.

Ciao,
Dscho

Johannes Schindelin [off-list ref] writes:

Hi,

On Fri, 27 Apr 2007, Jari Aalto wrote:

quoted

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

Jari Aalto, Fri, Apr 27, 2007 19:33:35 +0200:

quoted

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)

not a good use case: you can send text/plain mails with UTF-8 content
just as easily. And the patches will apply.

P.S. You ignored the suggestion to implement base64. Why?

Hi,

On Fri, 27 Apr 2007, Jari Aalto wrote:

Johannes Schindelin [off-list ref] writes:

quoted

On Fri, 27 Apr 2007, Jari Aalto wrote:

quoted

FEAURE REQUEST
--------------

Add sme option to git-format-path to encode thae patch content 
(MIME/base64)

[...]

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). 

That is no counterargument. I.e. it does not hold through basic scrutiny.

Ciao,
Dscho