All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jamie Lokier <jamie@shareable.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: joff@embeddedarm.com, Nicolas Pitre <nico@fluxnic.net>,
	linux-mtd <linux-mtd@lists.infradead.org>,
	H Hartley Sweeten <hartleys@visionengravers.com>,
	mcrapet@gmail.com,
	ARM Kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: Sending UTF-8 patches (was: [PATCH 2/2] Remove now-defunct ts7250 nand driver)
Date: Wed, 6 Jan 2010 23:27:11 +0000	[thread overview]
Message-ID: <20100106232711.GF24250@shareable.org> (raw)
In-Reply-To: <1262819289.3181.8784.camel@macbook.infradead.org>

David Woodhouse wrote:
> On Wed, 2010-01-06 at 23:05 +0000, Jamie Lokier wrote:
> > As I don't work with Git source and don't have enough time, I won't be
> > doing this, but I'd be delighted if someone else took the idea to the
> > Git people.  This thread could be used to explain why :-) 
> 
> I won't be bothering -- I'm quite happy just telling people not to send
> me legacy crap. There really is no justification for it, these days.

I suggest mutt users put this in .muttrc to work around git's inconsistency:

   set send_charset="us-ascii:utf-8"

If that's not acceptable, one could always add a hook to grep for a
patch when sending to decide what to do :-)

-- Jamie

WARNING: multiple messages have this Message-ID (diff)
From: jamie@shareable.org (Jamie Lokier)
To: linux-arm-kernel@lists.infradead.org
Subject: Sending UTF-8 patches (was: [PATCH 2/2] Remove now-defunct ts7250 nand driver)
Date: Wed, 6 Jan 2010 23:27:11 +0000	[thread overview]
Message-ID: <20100106232711.GF24250@shareable.org> (raw)
In-Reply-To: <1262819289.3181.8784.camel@macbook.infradead.org>

David Woodhouse wrote:
> On Wed, 2010-01-06 at 23:05 +0000, Jamie Lokier wrote:
> > As I don't work with Git source and don't have enough time, I won't be
> > doing this, but I'd be delighted if someone else took the idea to the
> > Git people.  This thread could be used to explain why :-) 
> 
> I won't be bothering -- I'm quite happy just telling people not to send
> me legacy crap. There really is no justification for it, these days.

I suggest mutt users put this in .muttrc to work around git's inconsistency:

   set send_charset="us-ascii:utf-8"

If that's not acceptable, one could always add a hook to grep for a
patch when sending to decide what to do :-)

-- Jamie

  reply	other threads:[~2010-01-06 23:27 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-05 21:59 [PATCH 2/2] Remove now-defunct ts7250 nand driver H Hartley Sweeten
2010-01-05 21:59 ` H Hartley Sweeten
2010-01-06 13:31 ` David Woodhouse
2010-01-06 13:31   ` David Woodhouse
2010-01-06 17:26   ` H Hartley Sweeten
2010-01-06 17:26     ` H Hartley Sweeten
2010-01-06 17:42     ` David Woodhouse
2010-01-06 17:42       ` David Woodhouse
2010-01-06 17:47       ` H Hartley Sweeten
2010-01-06 17:47         ` H Hartley Sweeten
2010-05-06 16:47         ` H Hartley Sweeten
2010-05-06 16:47           ` H Hartley Sweeten
2010-05-07  6:01           ` Artem Bityutskiy
2010-05-07  6:01             ` Artem Bityutskiy
2010-05-07 16:37             ` H Hartley Sweeten
2010-05-07 16:37               ` H Hartley Sweeten
2010-01-06 18:07   ` Sending UTF-8 patches (was: [PATCH 2/2] Remove now-defunct ts7250 nand driver) Jamie Lokier
2010-01-06 18:07     ` Jamie Lokier
2010-01-06 18:36     ` David Woodhouse
2010-01-06 18:36       ` David Woodhouse
2010-01-06 19:01       ` Nicolas Pitre
2010-01-06 19:01         ` Nicolas Pitre
2010-01-06 23:21       ` Jamie Lokier
2010-01-06 23:21         ` Jamie Lokier
2010-01-06 23:43         ` David Woodhouse
2010-01-06 23:43           ` David Woodhouse
2010-01-06 18:55     ` Nicolas Pitre
2010-01-06 18:55       ` Nicolas Pitre
2010-01-06 23:05       ` Jamie Lokier
2010-01-06 23:05         ` Jamie Lokier
2010-01-06 23:08         ` David Woodhouse
2010-01-06 23:08           ` David Woodhouse
2010-01-06 23:27           ` Jamie Lokier [this message]
2010-01-06 23:27             ` Jamie Lokier
2010-01-06 23:50             ` David Woodhouse
2010-01-06 23:50               ` David Woodhouse

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=20100106232711.GF24250@shareable.org \
    --to=jamie@shareable.org \
    --cc=dwmw2@infradead.org \
    --cc=hartleys@visionengravers.com \
    --cc=joff@embeddedarm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=mcrapet@gmail.com \
    --cc=nico@fluxnic.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 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.