From: Jeff King <peff@peff.net>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH] Documentation: quote double-dash in "<commit> -- <filename>" for AsciiDoc
Date: Tue, 28 Jun 2011 18:47:17 -0400 [thread overview]
Message-ID: <20110628224717.GC4192@sigill.intra.peff.net> (raw)
In-Reply-To: <20110628171748.GA11485@elie>
On Tue, Jun 28, 2011 at 12:17:49PM -0500, Jonathan Nieder wrote:
> As explained in v1.7.3-rc0~13^2 (Work around em-dash handling in newer
> AsciiDoc, 2010-08-23), outside of verbatim environments, newish
> versions of AsciiDoc will convert double hyphens to en dashes. Use
> the litdd syntax introduced by that patch to avoid such misformatting
> in sentences where "--" represents the two-character "end of options"
> argument that separates revision names from filename patterns.
Ugh. I just did a similar thing for "->". I really wish asciidoc would
not expand symbols inside backticks in paragraph mode.
> -to that of the last commit with `git reset HEAD -- <file>`,
> +to that of the last commit with `git reset HEAD {litdd} <file>`,
Does \-- work? That seems way more readable to me for people viewing the
source.
-Peff
next prev parent reply other threads:[~2011-06-28 22:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-28 17:17 [PATCH] Documentation: quote double-dash in "<commit> -- <filename>" for AsciiDoc Jonathan Nieder
2011-06-28 21:22 ` Junio C Hamano
2011-06-29 4:15 ` Jonathan Nieder
2011-06-28 22:47 ` Jeff King [this message]
2011-06-29 5:31 ` [PATCH v2 0/2] Documentation: quote double-dash " Jonathan Nieder
2011-06-29 5:35 ` [PATCH 1/2 maint] " Jonathan Nieder
2011-06-29 5:36 ` [PATCH 2/2] Documentation/i18n: " Jonathan Nieder
2011-06-29 10:42 ` Ævar Arnfjörð Bjarmason
2011-06-29 16:44 ` [PATCH] fixup! " Jonathan Nieder
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=20110628224717.GC4192@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.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).