From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Jiang Xin <worldhello.net@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, Git List <git@vger.kernel.org>
Subject: Re: [RFC] status: show tracking branch even no difference
Date: Wed, 07 Aug 2013 17:50:08 +0200 [thread overview]
Message-ID: <vpqr4e5h55b.fsf@anie.imag.fr> (raw)
In-Reply-To: <46fb1948a57990b0ea737401f2d60f654da4bb4f.1375890091.git.worldhello.net@gmail.com> (Jiang Xin's message of "Wed, 7 Aug 2013 23:42:01 +0800")
Jiang Xin <worldhello.net@gmail.com> writes:
> With this patch, "git status" will report relationship between current
> branch and its upstream counterpart even if there is no difference.
>
> $ git status
> # On branch master
> # Your branch is identical to its tracking branch: 'origin/master'.
Why not, but we try to say "remote-tracking branch" instead of just
"tracking". Adding "remote-" in your wording may make the line a bit
long, but it may be sufficient to say
# Your branch is identical to 'origin/master'
That's consistant with other messages like
# Your branch is ahead of '%s' by %d commits
(And this would deserve a test)
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2013-08-07 15:50 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-07 15:42 [RFC] status: show tracking branch even no difference Jiang Xin
2013-08-07 15:50 ` Matthieu Moy [this message]
2013-08-07 16:03 ` Jiang Xin
2013-08-08 5:40 ` [PATCH v2] status: always show tracking branch even no change Jiang Xin
2013-08-08 14:49 ` [PATCH v3] " Jiang Xin
2013-08-08 14:49 ` Jiang Xin
2013-08-09 21:18 ` Junio C Hamano
2013-08-10 15:05 ` Jiang Xin
2013-08-12 6:15 ` Junio C Hamano
2013-08-13 4:49 ` Jiang Xin
2013-08-13 4:53 ` [PATCH v5 1/2] branch: not report invalid tracking branch Jiang Xin
2013-08-14 15:21 ` Junio C Hamano
2013-08-15 2:14 ` Jiang Xin
2013-08-14 15:38 ` Junio C Hamano
2013-08-15 18:11 ` [PATCH v6 1/3] " Jiang Xin
2013-08-15 18:11 ` [PATCH v6 2/3] branch: report invalid tracking branch as broken Jiang Xin
2013-08-15 18:38 ` Junio C Hamano
2013-08-15 22:54 ` Junio C Hamano
2013-08-16 2:29 ` [PATCH v7 0/3] some enhancements for reporting branch tracking info Jiang Xin
[not found] ` <cover.1376620130.git.worldhello.net@gmail.com>
2013-08-16 2:29 ` [PATCH v7 1/3] branch: not report invalid tracking branch Jiang Xin
2013-08-16 2:29 ` [PATCH v7 2/3] branch: mark missing tracking branch as gone Jiang Xin
2013-08-21 7:37 ` Matthieu Moy
2013-08-22 0:00 ` Jiang Xin
2013-08-16 2:29 ` [PATCH v7 3/3] status: always show tracking branch even no change Jiang Xin
2013-08-18 19:51 ` [PATCH v7 0/3] some enhancements for reporting branch tracking info Junio C Hamano
2013-08-19 0:38 ` Jiang Xin
2013-08-26 7:02 ` [PATCH v8 0/2] " Jiang Xin
2013-08-26 7:02 ` [PATCH v8 1/2] branch: report invalid tracking branch as gone Jiang Xin
2013-08-26 7:02 ` [PATCH v8 2/2] status: always show tracking branch even no change Jiang Xin
2013-08-26 7:47 ` Jeremy Rosen
2013-08-26 8:04 ` Jiang Xin
2013-08-26 16:08 ` Junio C Hamano
2013-08-26 7:21 ` [PATCH v8 0/2] some enhancements for reporting branch tracking info Junio C Hamano
2013-08-15 18:11 ` [PATCH v6 3/3] status: always show tracking branch even no change Jiang Xin
2013-08-15 22:56 ` Junio C Hamano
2013-08-13 4:53 ` [PATCH v5 2/2] " Jiang Xin
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=vpqr4e5h55b.fsf@anie.imag.fr \
--to=matthieu.moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=worldhello.net@gmail.com \
/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.