From: Alex Riesen <raa.lkml@gmail.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <junkio@cox.net>
Subject: [PATCH] Beautify the output of send-pack a bit
Date: Mon, 12 Nov 2007 23:11:40 +0100 [thread overview]
Message-ID: <20071112221140.GD2918@steel.home> (raw)
Cluster the errors regarding ancestry violation and output them
in one batch, together with a hint to pull before pushing.
Signed-off-by: Alex Riesen <raa.lkml@gmail.com>
---
Catching trend...
send-pack.c | 33 ++++++++++++++++++++++-----------
1 files changed, 22 insertions(+), 11 deletions(-)
diff --git a/send-pack.c b/send-pack.c
index d56d980..e6da567 100644
--- a/send-pack.c
+++ b/send-pack.c
@@ -215,6 +215,7 @@ static int send_pack(int in, int out, struct remote *remote, int nr_refspec, cha
int ask_for_status_report = 0;
int allow_deleting_refs = 0;
int expect_status_report = 0;
+ struct ref *failed_refs = NULL, **failed_tail = &failed_refs;
/* No funny business with the matcher */
remote_tail = get_remote_heads(in, &remote_refs, 0, NULL, REF_NORMAL);
@@ -243,25 +244,27 @@ static int send_pack(int in, int out, struct remote *remote, int nr_refspec, cha
* Finally, tell the other end!
*/
new_refs = 0;
- for (ref = remote_refs; ref; ref = ref->next) {
+ ref = remote_refs;
+ remote_refs = NULL;
+ remote_tail = &remote_refs;
+ for (; ref; ref = ref->next) {
char old_hex[60], *new_hex;
int will_delete_ref;
if (!ref->peer_ref)
- continue;
-
+ goto remote_ok;
will_delete_ref = is_null_sha1(ref->peer_ref->new_sha1);
if (will_delete_ref && !allow_deleting_refs) {
error("remote does not support deleting refs");
ret = -2;
- continue;
+ goto remote_ok;
}
if (!will_delete_ref &&
!hashcmp(ref->old_sha1, ref->peer_ref->new_sha1)) {
if (verbose)
fprintf(stderr, "'%s': up-to-date\n", ref->name);
- continue;
+ goto remote_ok;
}
/* This part determines what can overwrite what.
@@ -297,13 +300,9 @@ static int send_pack(int in, int out, struct remote *remote, int nr_refspec, cha
* commits at the remote end and likely
* we were not up to date to begin with.
*/
- error("remote '%s' is not an ancestor of\n"
- " local '%s'.\n"
- " Maybe you are not up-to-date and "
- "need to pull first?",
- ref->name,
- ref->peer_ref->name);
ret = -2;
+ *failed_tail = ref;
+ failed_tail = &ref->next;
continue;
}
}
@@ -335,6 +334,18 @@ static int send_pack(int in, int out, struct remote *remote, int nr_refspec, cha
fprintf(stderr, "\n from %s\n to %s\n",
old_hex, new_hex);
}
+ remote_ok:
+ *remote_tail = ref;
+ remote_tail = &ref->next;
+ }
+ *remote_tail = NULL;
+ *failed_tail = NULL;
+
+ if (failed_refs) {
+ for (ref = failed_refs; ref; ref = ref->next)
+ error("remote '%s' is not an ancestor of local '%s'",
+ ref->name, ref->peer_ref->name);
+ fprintf(stderr, "Maybe you are not up-to-date and need to pull first?\n");
}
packet_flush(out);
--
1.5.3.5.648.g1e92c
next reply other threads:[~2007-11-12 22:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-12 22:11 Alex Riesen [this message]
2007-11-13 7:55 ` [PATCH] Beautify the output of send-pack a bit Jeff King
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=20071112221140.GD2918@steel.home \
--to=raa.lkml@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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).