Re: When does git check for branch-X being uptodate with origin/branch-X?
- From
Thomas Adam <thomas.adam22@gmail.com>
- Date
- Mar 21, 2016, 21:22 UTC
- Message-ID
- <CA+39Oz6A8WSFcXa4oALtuQK-uYJ+y43ZnFgqn3MRxQ4KSePWAw@mail.gmail.com>
- In-Reply-To
- <20160321211834.GA1068@sigill.intra.peff.net>
On 21 March 2016 at 21:18, Jeff King <peff@peff.net> wrote:
Show 5 quoted lines
> Again, just my opinion, but that looks awfully clunky. And it doesn't > address the other messages (you might be behind origin/branch-X by N > commits, or ahead by N, but only as of that particular date). Do we want > to annotate every message whose value was computed based on a tracking > branch?
Hmm. I would hope not. I'll wait for others to make a call on this, but it's about all I can suggest without significantly bloating the message which isn't desirable either.
Show 10 quoted lines
>> No one's suggesting that this message is removed, I'm not sure where >> you got that from? > > You said earlier: > >> [...]it's more a case of whether even printing that message is useful? > > I didn't know quite what you had in mind, which is why I asked. If we > all agree that removing it is a bad idea, then good, we don't have to > bother discussing that option. :)
Ah, oops! I was meaning more, whether to print the message in the case where the branch was uptodate, but now I appreciate it's cached. Apologies for the confusion.
-- Thomas Adam