From: Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com>
To: git@vger.kernel.org
Cc: Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com>
Subject: [PATCH v3] for-each-ref: Always check stat_tracking_info()'s return value.
Date: Fri, 2 Jan 2015 23:01:53 +0200 [thread overview]
Message-ID: <1420232513-13867-1-git-send-email-raphael.kubo.da.costa@intel.com> (raw)
The code handling %(upstream:track) and %(upstream:trackshort) assumed
it always had a valid branch that had been sanitized earlier in
populate_value(), and thus did not check the return value of the call to
stat_tracking_info().
While there is indeed some sanitization code that basically corresponds
to stat_tracking_info() returning 0 (no base branch set), the function
can also return -1 when the base branch did exist but has since then
been deleted.
In this case, num_ours and num_theirs had undefined values and a call to
`git for-each-ref --format="%(upstream:track)"` could print spurious
values such as
[behind -111794512]
[ahead 38881640, behind 5103867]
even for repositories with one single commit.
We now properly verify stat_tracking_info()'s return value and do not
print anything if it returns -1. This behavior also matches the
documentation ("has no effect if the ref does not have tracking
information associated with it").
Signed-off-by: Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com>
---
v3: Call `test_when_finished' as early as possible to clean up the
"parent_gone" branch.
builtin/for-each-ref.c | 11 +++++++++--
t/t6300-for-each-ref.sh | 15 +++++++++++++++
2 files changed, 24 insertions(+), 2 deletions(-)
diff --git a/builtin/for-each-ref.c b/builtin/for-each-ref.c
index 603a90e..52e6323 100644
--- a/builtin/for-each-ref.c
+++ b/builtin/for-each-ref.c
@@ -717,7 +717,10 @@ static void populate_value(struct refinfo *ref)
starts_with(name, "upstream")) {
char buf[40];
- stat_tracking_info(branch, &num_ours, &num_theirs);
+ if (stat_tracking_info(branch, &num_ours,
+ &num_theirs) != 1)
+ continue;
+
if (!num_ours && !num_theirs)
v->s = "";
else if (!num_ours) {
@@ -735,7 +738,11 @@ static void populate_value(struct refinfo *ref)
} else if (!strcmp(formatp, "trackshort") &&
starts_with(name, "upstream")) {
assert(branch);
- stat_tracking_info(branch, &num_ours, &num_theirs);
+
+ if (stat_tracking_info(branch, &num_ours,
+ &num_theirs) != 1)
+ continue;
+
if (!num_ours && !num_theirs)
v->s = "=";
else if (!num_ours)
diff --git a/t/t6300-for-each-ref.sh b/t/t6300-for-each-ref.sh
index bda354c..cba3454 100755
--- a/t/t6300-for-each-ref.sh
+++ b/t/t6300-for-each-ref.sh
@@ -335,6 +335,21 @@ test_expect_success 'Check that :track[short] cannot be used with other atoms' '
'
cat >expected <<EOF
+
+
+EOF
+
+test_expect_success 'Check that :track[short] works when upstream is gone' '
+ git branch --track to_delete master &&
+ git branch --track parent_gone to_delete &&
+ test_when_finished "git branch -D parent_gone" &&
+ git branch -D to_delete &&
+ git for-each-ref --format="%(upstream:track)" refs/heads/parent_gone >actual &&
+ git for-each-ref --format="%(upstream:trackshort)" refs/heads/parent_gone >>actual &&
+ test_cmp expected actual
+'
+
+cat >expected <<EOF
$(git rev-parse --short HEAD)
EOF
--
2.1.4
next reply other threads:[~2015-01-02 21:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-02 21:01 Raphael Kubo da Costa [this message]
2015-01-03 11:41 ` [PATCH v3] for-each-ref: Always check stat_tracking_info()'s return value Jeff King
2015-01-03 19:19 ` Raphael Kubo da Costa
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=1420232513-13867-1-git-send-email-raphael.kubo.da.costa@intel.com \
--to=raphael.kubo.da.costa@intel.com \
--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).