All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jiang Xin <worldhello.net@gmail.com>
Cc: Jeremy Rosen <jeremy.rosen@openwide.fr>,
	Git List <git@vger.kernel.org>,
	Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Subject: Re: [PATCH v8 2/2] status: always show tracking branch even no change
Date: Mon, 26 Aug 2013 09:08:50 -0700	[thread overview]
Message-ID: <xmqqvc2sigdp.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CANYiYbFNGZ=Y4BagNyrZEhO2c6O_J7g-MjA35fqBj2B9aXQf5w@mail.gmail.com> (Jiang Xin's message of "Mon, 26 Aug 2013 16:04:00 +0800")

Jiang Xin <worldhello.net@gmail.com> writes:

> 2013/8/26 Jeremy Rosen <jeremy.rosen@openwide.fr>:
>>
>> nitpicking, but shouldn't this be worded as "up to date" rather than "identical" ?
>>
>> The reason is that identical gives the idea that the two branch happen to be on the same
>> commit wheras "up to date" gives the idea that there is a special relationship between
>> these two particular branches. We are not just listing all branches on the same
>> commit as us, we are actively telling you about this branch because it's interesting
>> to you.
>
> That's better. I want to use 'up to date' in the beginning, but I don't know
> which prep. should be used. Now I realize I should:
>
>     s/identical to/up to date with/

Yeah, that, or "in sync with" which may be a bit shorter.

I'll queue with "up-to-date with", as "git grep 'up to date'" tells
me that it is less common than "git grep 'up-to-date'", for now.

Thanks.

  reply	other threads:[~2013-08-26 16:09 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
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 [this message]
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=xmqqvc2sigdp.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=Matthieu.Moy@grenoble-inp.fr \
    --cc=git@vger.kernel.org \
    --cc=jeremy.rosen@openwide.fr \
    --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.