git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Sixt <j6t@kdbg.org>
To: "Jason St. John" <jstjohn@purdue.edu>, git@vger.kernel.org
Subject: Re: [PATCH 2/4] Emphasize options and force ASCIIDOC escaping of "--"
Date: Sat, 09 Nov 2013 09:13:14 +0100	[thread overview]
Message-ID: <527DEE9A.2090503@kdbg.org> (raw)
In-Reply-To: <1383958133-4207-1-git-send-email-jstjohn@purdue.edu>

Am 09.11.2013 01:48, schrieb Jason St. John:
> -`--since=<date1>` limits to commits newer than `<date1>`, and using it
> -with `--grep=<pattern>` further limits to commits whose log message
> +'\--since=<date1>' limits to commits newer than `<date1>`, and using it
> +with '\--grep=<pattern>' further limits to commits whose log message

I don't think this kind of change goes in the right direction.
Currently, the general style seems to be that options are typeset in
monospaced font. I looked at git-merge and git-rebase (and git-log, of
course). But after your change, they are typeset in italics, in the HTML
version of the manual pages.

I did not find an advice on the preferred formatting, though, except for
the last sentence in Documentation/CodingGuidelines.

-- Hannes

  parent reply	other threads:[~2013-11-09  8:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-09  0:48 [PATCH 2/4] Emphasize options and force ASCIIDOC escaping of "--" Jason St. John
2013-11-09  0:48 ` [PATCH 3/4] Correct word usage of "timezone" in "Documentation" directory Jason St. John
2013-11-12 18:40   ` Junio C Hamano
2013-11-09  0:48 ` [PATCH 4/4] Correct word usage of "timezone" in "Documentation/RelNotes" directory Jason St. John
2013-11-09  1:02   ` Jonathan Nieder
2013-11-09  8:13 ` Johannes Sixt [this message]
2013-11-11 18:06 ` [PATCH 2/4] Emphasize options and force ASCIIDOC escaping of "--" Junio C Hamano
2013-11-12  8:38 ` Jeff King

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=527DEE9A.2090503@kdbg.org \
    --to=j6t@kdbg.org \
    --cc=git@vger.kernel.org \
    --cc=jstjohn@purdue.edu \
    /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).