All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jari Aalto <jari.aalto@cante.net>
To: git@vger.kernel.org
Subject: Re: FEATURE REQUEST: git-format-path: Add option to encode patch content
Date: Fri, 27 Apr 2007 20:33:35 +0300	[thread overview]
Message-ID: <d51pzpqo.fsf@cante.net> (raw)
In-Reply-To: Pine.LNX.4.64.0704271541010.12006@racer.site

Johannes Schindelin <Johannes.Schindelin@gmx.de> 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

  reply	other threads:[~2007-04-27 18:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-27 11:31 FEATURE REQUEST: git-format-path: Add option to encode patch content Jari Aalto
2007-04-27 13:43 ` Johannes Schindelin
2007-04-27 17:33   ` Jari Aalto [this message]
2007-04-27 19:29     ` Alex Riesen
2007-04-28  2:53     ` Johannes Schindelin
2007-04-27 19:49 ` Junio C Hamano
2007-04-27 20:35   ` Robin H. Johnson
2007-04-27 21:20   ` Carl Worth
2007-04-27 21:28     ` Junio C Hamano
2007-04-27 21:40     ` Linus Torvalds
2007-04-27 22:55       ` Carl Worth
2007-04-27 23:41         ` Linus Torvalds
2007-04-27 23:47           ` Linus Torvalds
2007-04-27 23:58           ` Carl Worth
2007-04-28  0:20             ` Linus Torvalds
2007-04-28  0:53               ` Junio C Hamano
2007-04-30 22:01               ` Carl Worth
2007-04-28  0:56     ` Junio C Hamano
2007-04-30 22:00       ` Carl Worth
2007-04-30 22:18         ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d51pzpqo.fsf@cante.net \
    --to=jari.aalto@cante.net \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.