All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiang Xin <worldhello.net@gmail.com>
To: Thomas Ackermann <th.acker@arcor.de>
Cc: Git List <git@vger.kernel.org>, Junio C Hamano <gitster@pobox.com>
Subject: Re: [Bug report] 'git status' always says "Your branch is up-to-date with 'origin/master'"
Date: Mon, 6 Jan 2014 13:31:08 +0800	[thread overview]
Message-ID: <CANYiYbG7Dh6npaMYajAeSMsR75SJM6kke9z7_4Q_z14nHY9KSg@mail.gmail.com> (raw)
In-Reply-To: <86886772.1529128.1388856329849.JavaMail.ngmail@webmail08.arcor-online.net>

2014/1/5 Thomas Ackermann <th.acker@arcor.de>:
> Since f223459 "status: always show tracking branch even no change"
> 'git status' (and 'git checkout master' always says
> "Your branch is up-to-date with 'origin/master'"
> even if 'origin/master' is way ahead from local 'master'.

Hi, Thomas

Can you provide your operations so that I can reproduce this issue?

In the commit you mentioned above, there was a new test case named
'checkout (up-to-date with upstream)' added in 't6040'. I also add two
test-cases locally in order to reproduce the issue you report, and run
them in arbitrary orders, but they all look fine:

    ok 4 - checkout (behind upstream)
    ok 5 - checkout (ahead upstream)
    ok 6 - checkout (diverged from upstream)
    ok 7 - checkout with local tracked branch
    ok 8 - checkout (upstream is gone)
    ok 9 - checkout (up-to-date with upstream)
    ok 10 - checkout (upstream is gone)
    ok 11 - checkout with local tracked branch
    ok 12 - checkout (diverged from upstream)
    ok 13 - checkout (ahead upstream)
    ok 14 - checkout (behind upstream)
    ok 15 - checkout (diverged from upstream)
    ok 16 - checkout (upstream is gone)
    ok 17 - checkout (ahead upstream)
    ok 18 - checkout with local tracked branch
    ok 19 - checkout (behind upstream)


The two additional test cases I used locally are:

    checkout_test1() {
    test_expect_success 'checkout (behind upstream)' '
            (
                    cd test && git checkout b3
            ) >actual &&
            test_i18ngrep "is behind .* by 1 commit, and can be
fast-forwarded" actual
    '
    }

    checkout_test_2() {
    test_expect_success 'checkout (ahead upstream)' '
            (
                    cd test && git checkout b4
            ) >actual &&
            test_i18ngrep "is ahead of .* by 2 commits" actual
    '
    }

-- 
Jiang Xin

      reply	other threads:[~2014-01-06  5:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-04 17:25 [Bug report] 'git status' always says "Your branch is up-to-date with 'origin/master'" Thomas Ackermann
2014-01-06  5:31 ` Jiang Xin [this message]

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=CANYiYbG7Dh6npaMYajAeSMsR75SJM6kke9z7_4Q_z14nHY9KSg@mail.gmail.com \
    --to=worldhello.net@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=th.acker@arcor.de \
    /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.