From: Junio C Hamano <gitster@pobox.com>
To: Stefan Beller <sbeller@google.com>
Cc: Thomas Adam <thomas.adam22@gmail.com>, Jeff King <peff@peff.net>,
git list <git@vger.kernel.org>
Subject: Re: When does git check for branch-X being uptodate with origin/branch-X?
Date: Mon, 21 Mar 2016 14:57:43 -0700 [thread overview]
Message-ID: <xmqq1t73lciw.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <CAGZ79kabn+pA4Fs2Y4E6Mwy-dKW6SZZ+LZK7_LjhqagcVc-xDg@mail.gmail.com> (Stefan Beller's message of "Mon, 21 Mar 2016 14:50:13 -0700")
Stefan Beller <sbeller@google.com> writes:
>> "branch-X is uptodate with origin/branch-X (as of DD-MM-YY HH:MM:SS)"
>
> Actually I like that feature of recording the last known time we fetched,
> I would have found that information useful in the past a few times. (unrelated
> to this exact message, but if we were to make this change, we would
> need to record
> the time somewhere, and that's what I would have wanted)
Like in reflog for refs/remotes/origin/branch-X?
next prev parent reply other threads:[~2016-03-21 21:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-21 20:21 When does git check for branch-X being uptodate with origin/branch-X? Thomas Adam
2016-03-21 20:28 ` Jeff King
2016-03-21 20:43 ` Thomas Adam
2016-03-21 20:47 ` Junio C Hamano
2016-03-21 20:50 ` Jeff King
2016-03-21 21:12 ` Thomas Adam
2016-03-21 21:18 ` Jeff King
2016-03-21 21:22 ` Thomas Adam
2016-03-21 21:50 ` Stefan Beller
2016-03-21 21:57 ` Junio C Hamano [this message]
2016-03-21 22:11 ` Stefan Beller
2016-03-21 22:42 ` Junio C Hamano
2016-03-21 23:18 ` Stefan Beller
2016-03-22 17:51 ` Philip Oakley
2016-03-21 20:48 ` Stefan Beller
2016-03-21 20:52 ` Junio C Hamano
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=xmqq1t73lciw.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=sbeller@google.com \
--cc=thomas.adam22@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 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).