git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: John Keeping <john@keeping.me.uk>, git@vger.kernel.org
Subject: Re: [PATCH v2] Documentation: don't link to example mail addresses
Date: Mon, 17 Dec 2012 07:02:54 -0500	[thread overview]
Message-ID: <20121217120253.GA21858@sigill.intra.peff.net> (raw)
In-Reply-To: <7vehippg91.fsf@alter.siamese.dyndns.org>

On Sun, Dec 16, 2012 at 06:24:58PM -0800, Junio C Hamano wrote:

> 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".

Typographically speaking, I would also be just as happy to use regular
double-quotes throughout.  But here's an example where they also caused
a problem (which was fixed by moving to smart-quotes in f34e9ed):

  http://thread.gmane.org/gmane.comp.version-control.git/163067

-Peff

  reply	other threads:[~2012-12-17 12:03 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
2012-12-17 12:02           ` Jeff King [this message]
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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20121217120253.GA21858@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=john@keeping.me.uk \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).