From: Michael J Gruber <git@drmicha.warpmail.net>
To: unlisted-recipients:; (no To-header on input)
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [RFC/WIP 0/2] Documentation clean-up: git commands
Date: Mon, 23 Mar 2009 15:31:16 +0100 [thread overview]
Message-ID: <49C79D34.3000408@drmicha.warpmail.net> (raw)
In-Reply-To: <1237818533-31577-1-git-send-email-git@drmicha.warpmail.net>
Michael J Gruber venit, vidit, dixit 23.03.2009 15:28:
> In current git documentation, git commands are still written in various
> styles: with and without dash, unformatted and formatted with `, ' or ".
>
> I propose to use `git command` consistently. In asciidoc, backticks are
> for commands, ticks for paths. [Quotes should be like ``this''.]
>
> A first step is reaching a consistent use of backticks. A second step
> would be sed magic to get rid of the dashes in the text, not in the
> links (linkgit:...).
>
> Patch 1 is a preparation patch where I spotted the use of a command with
> "git" in an instance where it looks very inconsistent. (It feels OK when
s/with/without/
Sorry :|
next prev parent reply other threads:[~2009-03-23 14:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-23 14:28 [RFC/WIP 0/2] Documentation clean-up: git commands Michael J Gruber
2009-03-23 14:28 ` [RFC/WIP 1/2] Documentation: fix minor inconsistency Michael J Gruber
2009-03-23 14:28 ` [RFC/WIP 2/2] Documentation: format git commands consistently Michael J Gruber
2009-03-23 14:44 ` [RFC/WIP 1/2] Documentation: fix minor inconsistency Matthieu Moy
2009-03-23 14:56 ` Michael J Gruber
2009-03-23 14:31 ` Michael J Gruber [this message]
2009-03-23 16:22 ` [RFC/WIP 0/2] Documentation clean-up: git commands Junio C Hamano
2009-03-23 16:35 ` Michael J Gruber
2009-03-23 23:13 ` Chris Johnsen
2009-03-24 3:34 ` Jeff King
2009-03-24 8:24 ` Michael J Gruber
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=49C79D34.3000408@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 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.