From: Junio C Hamano <junkio@cox.net>
To: git@vger.kernel.org
Subject: [PATCH] Return error when not checking out an entry due to dirtiness.
Date: Mon, 03 Oct 2005 22:11:03 -0700 [thread overview]
Message-ID: <7vu0fxhno8.fsf@assigned-by-dhcp.cox.net> (raw)
Without -f flag, 'git-checkout-index foo.c' issued an error message
when foo.c already existed in the working tree and did not match index.
However it did not return an error from the underlying checkout_entry()
function and resulted in a successful exit(0).
Signed-off-by: Junio C Hamano <junkio@cox.net>
---
* I've made sure that the existing scripts do not use
checkout-index without -f in a way that could be affected by
this change. However, third-party scripts may be affected by
this. Cogito and StGIT should be OK -- they either run
checkout with -f, do not check the error return when it does
not use -f, or runs checkout without -f in an empty working
tree.
checkout-index.c | 11 ++++++++---
entry.c | 2 +-
2 files changed, 9 insertions(+), 4 deletions(-)
5a166f6a9d1b7ca2de673139fbfc4112b1b2e308
diff --git a/checkout-index.c b/checkout-index.c
--- a/checkout-index.c
+++ b/checkout-index.c
@@ -63,15 +63,20 @@ static int checkout_file(const char *nam
static int checkout_all(void)
{
- int i;
+ int i, errs;
- for (i = 0; i < active_nr ; i++) {
+ for (errs = i = 0; i < active_nr ; i++) {
struct cache_entry *ce = active_cache[i];
if (ce_stage(ce))
continue;
if (checkout_entry(ce, &state) < 0)
- return -1;
+ errs++;
}
+ if (errs)
+ /* we have already done our error reporting.
+ * exit with the same code as die().
+ */
+ exit(128);
return 0;
}
diff --git a/entry.c b/entry.c
--- a/entry.c
+++ b/entry.c
@@ -132,7 +132,7 @@ int checkout_entry(struct cache_entry *c
if (!state->force) {
if (!state->quiet)
fprintf(stderr, "git-checkout-index: %s already exists\n", path);
- return 0;
+ return -1;
}
/*
next reply other threads:[~2005-10-04 5:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-04 5:11 Junio C Hamano [this message]
2005-10-04 19:52 ` [PATCH] Return error when not checking out an entry due to dirtiness Horst von Brand
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=7vu0fxhno8.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.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