From: Matt Kraai <kraai@ftbfs.org>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: gitster@pobox.com, git@vger.kernel.org
Subject: Re: [PATCH] commit: quote the user name in the example
Date: Wed, 24 Feb 2010 06:19:35 -0800 [thread overview]
Message-ID: <20100224141935.GC2709@ftbfs.org> (raw)
In-Reply-To: <4B84DA03.1040809@viscovery.net>
On Wed, Feb 24, 2010 at 08:49:23AM +0100, Johannes Sixt wrote:
> Actually, I would prefer that the suggested command is
>
> git config --global user.name "Your Name"
>
> i.e., with double-quotes, because then the suggestion is also correct for
> Windows users who run git from CMD: in this environment, single-quotes do
> not quote, but double-quotes do.
I've justed submitted a modified version of the patch that uses
double-quotes. Thanks for the suggestion.
--
Matt http://ftbfs.org/kraai
prev parent reply other threads:[~2010-02-24 14:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-24 2:54 [PATCH] commit: quote the user name in the example Matt Kraai
2010-02-24 3:00 ` Junio C Hamano
2010-02-24 7:49 ` Johannes Sixt
2010-02-24 14:18 ` Matt Kraai
2010-02-24 14:19 ` Matt Kraai [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=20100224141935.GC2709@ftbfs.org \
--to=kraai@ftbfs.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j.sixt@viscovery.net \
/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).