All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: "Uwe Kleine-König" <ukleinek@informatik.uni-freiburg.de>
Cc: "Shawn O. Pearce" <spearce@spearce.org>, git@vger.kernel.org
Subject: Re: [PATCH 2/2] Correct some language in fast-import documentation.
Date: Thu, 08 Feb 2007 00:50:34 -0800	[thread overview]
Message-ID: <7vveidyqw5.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20070208082850.GA4334@informatik.uni-freiburg.de> (Uwe =?utf-8?Q?Kleine-K=C3=B6nig's?= message of "Thu, 8 Feb 2007 09:28:50 +0100")

Uwe Kleine-König  <ukleinek@informatik.uni-freiburg.de> writes:

> Shawn O. Pearce wrote:
>> Minor documentation improvements, as suggested on the Git mailing
>> list by Horst H. von Brand and Karl Hasselstr~A(P)m.
> you have an encoding problem here     ---------^
>
> That "o umlaut" seems to be UTF-8 encoded, but the headers of you mail
> claim iso-8859-1.

I noticed it, too.  This seems to be purely between the
format-patch output and the mailing list.  In Shawn's tree, the
corresponding commit f842fdb0 does not have the encoding
problem.

As Shawn's tree currently has only these two commits on top of
what my tree already has, I do not mind pulling from it.  It
would make life easier for people who are following his tree.

  reply	other threads:[~2007-02-08  8:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-08  7:58 [PATCH 2/2] Correct some language in fast-import documentation Shawn O. Pearce
2007-02-08  8:28 ` Uwe Kleine-König
2007-02-08  8:50   ` Junio C Hamano [this message]
2007-02-08 18:32     ` Shawn O. Pearce
2007-02-08 18:39       ` Johannes Schindelin
2007-02-08 20:31         ` Uwe Kleine-König
2007-02-08 20:53           ` Johannes Schindelin
2007-02-08 22:07             ` Jakub Narebski
2007-02-08 22:11               ` Shawn O. Pearce

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=7vveidyqw5.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=git@vger.kernel.org \
    --cc=spearce@spearce.org \
    --cc=ukleinek@informatik.uni-freiburg.de \
    /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.