From: Samuel Tardieu <sam@rfc1149.net>
To: git@vger.kernel.org
Subject: Unclear error message in "git remote update"
Date: Sun, 09 Mar 2008 13:37:55 +0100 [thread overview]
Message-ID: <2008-03-09-13-37-55+trackit+sam@rfc1149.net> (raw)
One of my colleague seems to have destroyed one of its head in his
private repository. When fetching from it through "git remote update"
using next, the repository name is not output:
% git remote update
error: refs/heads/2.0-uobjects points nowhere!
Using master, I get:
% git remote update
Updating core
Updating matthieu
error: refs/heads/2.0-uobjects points nowhere!
Updating origin
which is IMO much clearer. Also, I like seeing what remote repository
it is updating from in case anything gets stuck or slow.
Any objection to reinstating the message as does the following patch?
From: Samuel Tardieu <sam@rfc1149.net>
Date: Sun, 9 Mar 2008 13:33:44 +0100
Subject: [PATCH] builtin remote update: print remote name being fetched from
Reinstate the message "Updating <name>" in git remote update.
Signed-off-by: Samuel Tardieu <sam@rfc1149.net>
---
builtin-remote.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/builtin-remote.c b/builtin-remote.c
index ca3bf26..65d90e1 100644
--- a/builtin-remote.c
+++ b/builtin-remote.c
@@ -46,6 +46,7 @@ static int opt_parse_track(const struct option *opt, const char *arg, int not)
static int fetch_remote(const char *name)
{
const char *argv[] = { "fetch", name, NULL };
+ printf("Updating %s\n", name);
if (run_command_v_opt(argv, RUN_GIT_CMD))
return error("Could not fetch %s", name);
return 0;
--
1.5.4.3.611.g29c00
next reply other threads:[~2008-03-09 12:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-09 12:37 Samuel Tardieu [this message]
2008-03-09 20:52 ` Unclear error message in "git remote update" Johannes Schindelin
2008-03-12 5:10 ` Junio C Hamano
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=2008-03-09-13-37-55+trackit+sam@rfc1149.net \
--to=sam@rfc1149.net \
--cc=git@vger.kernel.org \
/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).