From: Junio C Hamano <gitster@pobox.com>
To: John Keeping <john@keeping.me.uk>
Cc: Jeff King <peff@peff.net>, git@vger.kernel.org
Subject: Re: [PATCH v2] Documentation: don't link to example mail addresses
Date: Sun, 16 Dec 2012 18:24:58 -0800 [thread overview]
Message-ID: <7vehippg91.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20121216140029.GE2725@river.lan> (John Keeping's message of "Sun, 16 Dec 2012 14:00:29 +0000")
John Keeping <john@keeping.me.uk> writes:
> diff --git a/Documentation/git-fast-import.txt b/Documentation/git-fast-import.txt
> index d1844ea..68bca1a 100644
> --- a/Documentation/git-fast-import.txt
> +++ b/Documentation/git-fast-import.txt
> @@ -427,7 +427,7 @@ they made it.
>
> Here `<name>` is the person's display name (for example
> ``Com M Itter'') and `<email>` is the person's email address
> -(``cm@example.com''). `LT` and `GT` are the literal less-than (\x3c)
> +(``\cm@example.com''). `LT` and `GT` are the literal less-than (\x3c)
I seem to be getting
(<tt>`\cm@example.com''). `LT</tt> and <tt>GT</tt> are the literal less-than (\x3c)
out of this part in the resulting HTML output, which is probably not
what you wanted to see.
I have a feeling that it might be a better solution to stop using
these pretty quotes. It's not like we use them a lot and a quick
scanning of "git grep '``'" output seems to tell me that many of
them should be `monospace output`, and the rest (mostly references
to section headers) can be "Section".
next prev parent reply other threads:[~2012-12-17 2:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-15 15:03 [PATCH] Documentation: don't link to example mail addresses John Keeping
2012-12-15 17:20 ` Jeff King
2012-12-15 18:00 ` Junio C Hamano
2012-12-15 18:24 ` John Keeping
2012-12-16 12:04 ` Jeff King
2012-12-16 14:00 ` [PATCH v2] " John Keeping
2012-12-16 18:48 ` Junio C Hamano
2012-12-17 2:24 ` Junio C Hamano [this message]
2012-12-17 12:02 ` Jeff King
2012-12-17 19:57 ` Junio C Hamano
2012-12-17 5:29 ` [PATCH] " Junio C Hamano
2012-12-17 9:44 ` John Keeping
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=7vehippg91.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=john@keeping.me.uk \
--cc=peff@peff.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.