From: David Woodhouse <dwmw2@infradead.org>
To: Matt Mackall <mpm@selenic.com>
Cc: Matti Aarnio <matti.aarnio@zmailer.org>, Mark Lord <lkml@rtr.ca>,
Greg Kroah-Hartman <gregkh@suse.de>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
torvalds@linux-foundation.org, stable@kernel.org
Subject: Re: Linux 2.6.23.2
Date: Fri, 16 Nov 2007 18:35:30 -0500 [thread overview]
Message-ID: <1195256130.2533.156.camel@shinybook.infradead.org> (raw)
In-Reply-To: <20071116195745.GC17536@waste.org>
On Fri, 2007-11-16 at 13:57 -0600, Matt Mackall wrote:
> What is the proper encoding for a patch that contains hunks in
> multiple character sets?
That should only happen when we're fixing legacy crap to become UTF-8 --
and in that case, it's probably best to just handle it with a git-pull
rather than mailing patches around.
Normally, we should see only UTF-8 in patches.
--
dwmw2
next prev parent reply other threads:[~2007-11-16 23:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-16 18:37 Linux 2.6.23.8 Greg Kroah-Hartman
2007-11-16 18:38 ` Greg Kroah-Hartman
2007-11-16 18:39 ` Linux 2.6.23.2 Greg Kroah-Hartman
2007-11-16 18:39 ` Greg Kroah-Hartman
2007-11-16 19:35 ` Mark Lord
2007-11-16 19:39 ` Matti Aarnio
2007-11-16 19:57 ` Matt Mackall
2007-11-16 23:35 ` David Woodhouse [this message]
2007-11-18 1:38 ` Krzysztof Halasa
2007-11-16 20:10 ` Greg KH
2007-11-16 18:44 ` Linux 2.6.23.3 Greg Kroah-Hartman
2007-11-16 18:44 ` Greg Kroah-Hartman
2007-11-16 23:15 ` Michael Tokarev
2007-11-17 1:03 ` Greg KH
2007-11-16 18:46 ` Linux 2.6.23.4 Greg Kroah-Hartman
2007-11-16 18:46 ` Greg Kroah-Hartman
2007-11-16 18:47 ` Linux 2.6.23.5 Greg Kroah-Hartman
2007-11-16 18:47 ` Greg Kroah-Hartman
2007-11-16 18:48 ` Linux 2.6.23.6 Greg Kroah-Hartman
2007-11-16 18:49 ` Greg Kroah-Hartman
2007-11-16 18:50 ` Linux 2.6.23.7 Greg Kroah-Hartman
2007-11-16 18:50 ` Greg Kroah-Hartman
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=1195256130.2533.156.camel@shinybook.infradead.org \
--to=dwmw2@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
--cc=matti.aarnio@zmailer.org \
--cc=mpm@selenic.com \
--cc=stable@kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®