From: Stefan Tatschner <stefan@sevenbyte.org>
To: gitster@pobox.com
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Documentation: Fix inconsistent quotes
Date: Thu, 14 May 2015 11:14:17 +0200 [thread overview]
Message-ID: <1431594857.15159.4.camel@sevenbyte.org> (raw)
In-Reply-To: <1430330932-10578-1-git-send-email-stefan@sevenbyte.org>
On Wed, 2015-04-29 at 20:08 +0200, Stefan Tatschner wrote:
> While reading 'man git' I realized that the highlighting of the
> environment variables is not consistent. This patch adds missing
> single
> quotes and substitutes backticks with the proper quotes as well.
Since currently there are some patches around which aim to improve the
documentation, may I ask about the status of this patch? Should I
improve/modify something, or is it actually not needed?
Thanks,
Stefan
prev parent reply other threads:[~2015-05-14 9:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-29 18:08 [PATCH] Documentation: Fix inconsistent quotes Stefan Tatschner
2015-04-29 18:51 ` Jeff King
2015-04-29 19:09 ` Jonathan Nieder
2015-04-29 20:04 ` Jeff King
2015-04-29 20:13 ` Junio C Hamano
2015-04-29 20:32 ` Jeff King
2015-05-14 9:14 ` Stefan Tatschner [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1431594857.15159.4.camel@sevenbyte.org \
--to=stefan@sevenbyte.org \
--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 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).