git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: "PAYRE NATHAN p1508475" <second.payre@gmail.com>,
	git@vger.kernel.org,
	"PAYRE NATHAN p1508475" <nathan.payre@etu.univ-lyon1.fr>,
	"MOY Matthieu" <matthieu.moy@univ-lyon1.fr>,
	"Daniel Bensoussan" <daniel.bensoussan--bohm@etu.univ-lyon1.fr>,
	"Timothee Albertin" <timothee.albertin@etu.univ-lyon1.fr>,
	"Robert P. J. Day" <rpjday@crashcourse.ca>,
	"René Scharfe" <l.s.r@web.de>
Subject: Re: [PATCH v3] Documentation/git-config.txt: reword missleading sentence
Date: Thu, 19 Oct 2017 13:58:43 +0900	[thread overview]
Message-ID: <xmqqa80nka2k.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20171018220530.h6dgneq2dvhmwfeu@aiede.mtv.corp.google.com> (Jonathan Nieder's message of "Wed, 18 Oct 2017 15:12:48 -0700")

Jonathan Nieder <jrnieder@gmail.com> writes:

> Or, to capture the other changes being made at the same time:
>
> 	config doc: clarify "git config --path" example
>
> Thanks for working on this.

Yup.  I'll queue with the above subject; all the suggestions in your
message were sensible, so I'll take them when I do so.

> By the way, should the initial `git config` be 'git config' (in
> italics instead of monospace)?  I don't see `git config` anywhere else
> in the file and there are a lot of instances of 'git config'.

We want to use monospace for something we expect users to type
verbatim while following the description along, and highlight
important terms that are being explained by typesetting in italics.
This one can go either way, so I'll keep it as posted.

Thanks.



      reply	other threads:[~2017-10-19  4:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-05  8:17 [PATCH] Documentation/git-config.txt: reword missleading sentence PAYRE NATHAN p1508475
2017-10-05 10:13 ` Junio C Hamano
2017-10-10  8:19   ` Nathan PAYRE
2017-10-10  8:48     ` Junio C Hamano
2017-10-12  9:17       ` [PATCH v2] " second.payre
2017-10-13  0:23         ` Junio C Hamano
2017-10-13  8:32           ` Moy Matthieu
2017-10-13 12:04             ` Junio C Hamano
2017-10-18 20:27               ` [PATCH v3] " PAYRE NATHAN p1508475
2017-10-18 22:12                 ` Jonathan Nieder
2017-10-19  4:58                   ` Junio C Hamano [this message]

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=xmqqa80nka2k.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=daniel.bensoussan--bohm@etu.univ-lyon1.fr \
    --cc=git@vger.kernel.org \
    --cc=jrnieder@gmail.com \
    --cc=l.s.r@web.de \
    --cc=matthieu.moy@univ-lyon1.fr \
    --cc=nathan.payre@etu.univ-lyon1.fr \
    --cc=rpjday@crashcourse.ca \
    --cc=second.payre@gmail.com \
    --cc=timothee.albertin@etu.univ-lyon1.fr \
    /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).