From: Junio C Hamano <gitster@pobox.com>
To: Richard Hartmann <richih.mailinglist@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Fix 'Cloning into' message
Date: Thu, 27 Oct 2011 10:39:09 -0700 [thread overview]
Message-ID: <7vvcraz64i.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <1319734013-8956-1-git-send-email-richih.mailinglist@gmail.com> (Richard Hartmann's message of "Thu, 27 Oct 2011 18:46:53 +0200")
Richard Hartmann <richih.mailinglist@gmail.com> writes:
> Without this patch,
>
> git clone foo .
>
> results in this:
>
> Cloning into ....
> done.
>
> With it:
>
> Cloning into '.'...
> done.
>
> Signed-off-by: Richard Hartmann <richih.mailinglist@gmail.com>
We try to be consistent and many places do quote user supplied paths in
pair of single quotes in human readable messages, and this is in line with
that pattern.
$ git clone foo "joey's foo"
would result in
Cloning into 'joey's foo'...
but that is probably Ok ;-)
Thanks.
next prev parent reply other threads:[~2011-10-27 17:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-26 17:05 [PATCH] Fix 'Cloning into' message Richard Hartmann
2011-10-27 16:46 ` Richard Hartmann
2011-10-27 17:39 ` Junio C Hamano [this message]
2011-10-27 18:34 ` Richard Hartmann
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=7vvcraz64i.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=richih.mailinglist@gmail.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).