All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pete Harlan <pgit@pcharlan.com>
To: Jeff King <peff@peff.net>
Cc: git list <git@vger.kernel.org>
Subject: [PATCH v2 1/2] clone: have progress report mention top level dir, not git dir
Date: Sun, 09 May 2010 13:10:17 -0700	[thread overview]
Message-ID: <4BE716A9.9060608@pcharlan.com> (raw)
In-Reply-To: <4BE7166A.5030107@pcharlan.com>

"git clone foo bar" currently reports "Cloning into
/path/to/bar/.git".  Change this message to "Cloning into bar" to more
closely match the user's expectation.

Signed-off-by: Pete Harlan <pgit@pcharlan.com>
---
 builtin/clone.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/builtin/clone.c b/builtin/clone.c
index 0bedde4..306aacf 100644
--- a/builtin/clone.c
+++ b/builtin/clone.c
@@ -464,7 +464,7 @@ int cmd_clone(int argc, const char **argv, const char *prefix)
 	set_git_dir(make_absolute_path(git_dir));
 
 	if (0 <= option_verbosity)
-		printf("Cloning into %s...\n", get_git_dir());
+		printf("Cloning into %s...\n", dir);
 	init_db(option_template, INIT_DB_QUIET);
 
 	/*
-- 
1.7.1.14.gcafbfa.dirty

  reply	other threads:[~2010-05-09 20:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-09  1:23 [PATCH/RFC] clone: have progress report mention top level dir, not git dir Pete Harlan
2010-05-09 11:02 ` Jeff King
2010-05-09 20:09   ` [PATCH v2 0/2] clone: simplify progress message Pete Harlan
2010-05-09 20:10     ` Pete Harlan [this message]
2010-05-09 20:11     ` [PATCH v2 2/2] clone: add bare clone to the " Pete Harlan
2010-05-09 22:15     ` [PATCH v2 0/2] clone: simplify " Junio C Hamano
2010-05-09 23:10       ` Pete Harlan
2010-05-10  5:47     ` Jeff King
2010-05-10 10:31       ` Michael J Gruber
2010-05-10 14:46         ` [PATCH] clone: report check out for non-bare clones Michael J Gruber
2010-05-12  1:55           ` Junio C Hamano
2010-05-12  7:59             ` Michael J Gruber
2010-05-10 23:22         ` [PATCH v2 0/2] clone: simplify progress message Pete Harlan
2010-05-11  7:27           ` 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=4BE716A9.9060608@pcharlan.com \
    --to=pgit@pcharlan.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.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 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.