From: "Øystein Walle" <oystwa@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] Improve user-manual html and pdf formatting
Date: Sat, 4 Jan 2014 21:38:48 +0000 (UTC) [thread overview]
Message-ID: <loom.20140104T223713-502@post.gmane.org> (raw)
In-Reply-To: 20140104211834.GC12251@google.com
Jonathan Nieder <jrnieder <at> gmail.com> writes:
>
> Hi,
>
> Thomas Ackermann wrote:
>
> > --- a/Documentation/user-manual.txt
> > +++ b/Documentation/user-manual.txt
> > <at> <at> -1,5 +1,5 <at> <at>
> > -Git User Manual
> > +Git User Manual
>
> Why?
>
> Puzzled,
> Jonathan
>
That's a Unicode Byte Order Mark. In UTF-8 it serves no purpose except
to indicate that a file is in fact UTF-8. A job which most editors
don't need help with.
See http://en.wikipedia.org/wiki/Byte_order_mark
Øsse
next prev parent reply other threads:[~2014-01-04 21:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-04 9:07 [PATCH] Improve user-manual html and pdf formatting Thomas Ackermann
2014-01-04 21:18 ` Jonathan Nieder
2014-01-04 21:38 ` Øystein Walle [this message]
2014-01-04 21:54 ` Andreas Schwab
2014-01-04 22:12 ` Øystein Walle
2014-01-05 8:22 ` Aw: " Thomas Ackermann
2014-01-06 17:20 ` Junio C Hamano
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=loom.20140104T223713-502@post.gmane.org \
--to=oystwa@gmail.com \
--cc=git@vger.kernel.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).