git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Riesen <raa.lkml@gmail.com>
To: Jari Aalto <jari.aalto@cante.net>
Cc: git@vger.kernel.org
Subject: Re: FEATURE REQUEST: git-format-path: Add option to encode patch content
Date: Fri, 27 Apr 2007 21:29:17 +0200	[thread overview]
Message-ID: <20070427192917.GA23169@steel.home> (raw)
In-Reply-To: <d51pzpqo.fsf@cante.net>

Jari Aalto, Fri, Apr 27, 2007 19:33:35 +0200:
> > 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?

  reply	other threads:[~2007-04-27 19:29 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
2007-04-27 19:29     ` Alex Riesen [this message]
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=20070427192917.GA23169@steel.home \
    --to=raa.lkml@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jari.aalto@cante.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).