git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Matti Aarnio <matti.aarnio@zmailer.org>
Cc: git@vger.kernel.org
Subject: Re: Missing MIME-headers in git-email-tool ..
Date: Tue, 30 Oct 2007 12:07:14 +0000 (GMT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0710301157290.4362@racer.site> (raw)
In-Reply-To: <20071030112750.GA6372@mea-ext.zmailer.org>

Hi,

[please Cc: me]

On Tue, 30 Oct 2007, Matti Aarnio wrote:

> On Tue, Oct 30, 2007 at 10:31:41AM +0000, Johannes Schindelin wrote:
> 
> > On Tue, 30 Oct 2007, Matti Aarnio wrote:
> > 
> > > The  git-send-email  does send posts without any sort of MIME labeling:
> > > 
> > >   From: / To: removed
> > > 
> > >   Subject: [PATCH 0/2] Blackfin I2C/TWI driver updates
> > >   Date: Tue, 30 Oct 2007 17:33:15 +0800
> > >   Message-Id: <1193736797-9005-1-git-send-email-bryan.wu@analog.com>
> > >   X-Mailer: git-send-email 1.5.3.4
> > >   Precedence: bulk
> > > 
> > > 
> > > which per MIME rules means that the message in question is equivalent
> > > to one with header labels:
> > > 
> > >   MIME-Version: 1.0
> > >   Content-Type: text/plain; charset=US-ASCII
> > >   Content-Transfer-Encoding: 7bit
> > 
> > AFAICT MIME headers are only added when needed.  (But that might only 
> > apply to format-patch; however, if you signed off with your name, all 
> > should be well.)
> 
> I wish that were true..   We (VGER's Postmasters that is) would not see
> so much rejections from all over the places...   Would it motivate you
> if we sent all GIT caused ones to you ?

Heh.

I'm not a send-mail user myself, so I did not ever have any reason to dive 
into its source code.  Sorry.

I understand your pain.  But as we assume UTF-8 in git if no other 
encoding is selected, I think it makes more sense to default to UTF-8.

That said, I actually like the behaviour which I think is intended, to not 
specify anything when the message can be interpreted as US-ASCII.

BTW I tried to find anything in the message you referenced which would 
make it non-ASCII, but I did not find anything.  But then, I am not 
subscribed to the lkml, and can only get stripped down versions of the 
mails via marc or kerneltrap.

Any send-email gurus want to join into this discussion?

Ciao,
Dscho

  reply	other threads:[~2007-10-30 12:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-30  9:53 Missing MIME-headers in git-email-tool Matti Aarnio
2007-10-30 10:31 ` Johannes Schindelin
2007-10-30 11:27   ` Matti Aarnio
2007-10-30 12:07     ` Johannes Schindelin [this message]
2007-10-30 14:06 ` Jeff King
2007-10-30 14:09   ` Jeff King

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=Pine.LNX.4.64.0710301157290.4362@racer.site \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=matti.aarnio@zmailer.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 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).