git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Santi Béjar" <sbejar@gmail.com>
To: "Karl Hasselström" <kha@treskal.com>
Cc: "J. Bruce Fields" <bfields@citi.umich.edu>,
	"Junio C Hamano" <junkio@cox.net>,
	git@vger.kernel.org
Subject: Re: [PATCH 4/6] user-manual: fix .gitconfig editing examples
Date: Mon, 7 May 2007 11:33:28 +0200	[thread overview]
Message-ID: <8aa486160705070233g4e9ed55cx747ab34426c9d369@mail.gmail.com> (raw)
In-Reply-To: <20070507092704.GA1106@diana.vm.bytemark.co.uk>

On 5/7/07, Karl Hasselström <kha@treskal.com> wrote:
> On 2007-05-07 09:29:23 +0200, Santi Béjar wrote:
>
> > I see it OK. Both in the mail and in the repo.
>
> The headers said, among other things,
>
>   Content-Transfer-Encoding: QUOTED-PRINTABLE
>   Content-Type: TEXT/PLAIN; charset=ISO-8859-1
>

My headers say:

Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit

> and the raw text of the body was
>
>   Santi B=C3=A9jar points out that
>
> Note how the "é" in your name is encoded with two bytes.
>
> But if it's not broken in the repository, it's probably nothing to
> worry about. :-)

Or +1 for a git log that uses .mailcap in the commit message :-D

Santi

  reply	other threads:[~2007-05-07  9:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-07  6:42 [PATCH 4/6] user-manual: fix .gitconfig editing examples Karl Hasselström
2007-05-07  7:29 ` Santi Béjar
2007-05-07  9:27   ` Karl Hasselström
2007-05-07  9:33     ` Santi Béjar [this message]
2007-05-07  9:42       ` Karl Hasselström
     [not found] <11785148422793-git-send-email->
     [not found] ` <11785148433801-git-send-email->
     [not found]   ` <11785148442263-git-send-email->
     [not found]     ` <1178514845119-git-send-email->
2007-05-07  5:14       ` J. Bruce Fields

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=8aa486160705070233g4e9ed55cx747ab34426c9d369@mail.gmail.com \
    --to=sbejar@gmail.com \
    --cc=bfields@citi.umich.edu \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=kha@treskal.com \
    /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).