From: Junio C Hamano <gitster@pobox.com>
To: Robert Dailey <rcdailey.lists@gmail.com>
Cc: Git <git@vger.kernel.org>
Subject: Re: Why do dates in refspecs require the reflog?
Date: Tue, 30 Dec 2014 12:47:02 -0800 [thread overview]
Message-ID: <xmqq1tngsw55.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CAHd499Cvy=zi=9utoZ2bEgdSUTjkveHMP2OvVFPBHq7W2MuoZQ@mail.gmail.com> (Robert Dailey's message of "Tue, 30 Dec 2014 14:12:15 -0600")
Robert Dailey <rcdailey.lists@gmail.com> writes:
> ... how can I view the
> contents of a file at a specified relative time frame ...
"git log --until=A --since=B master" asks Git to start traversing
the history backward from the tip of your current 'master' branch,
without showing anything until it finds a commit with timestamp A
(or before), and then show the commits it finds during the traversal
until it finds a commit with timestamp B (or before) and then stop.
Which I think is the closest thing you are asking for.
Note that there is *no* guarantee that any of these commits you find
that way was actually at the tip of the public history (i.e. the one
casual users would have seen after running "git clone" at that time).
The committer may have started working at around time B, worked for
quite some time, and pushed the result out way after time A. Then
the first time general public observed the commits you find in that
time range could be after time A by many weeks, which is perfectly
normal in the real, distributed, world.
next prev parent reply other threads:[~2014-12-30 20:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-30 20:12 Why do dates in refspecs require the reflog? Robert Dailey
2014-12-30 20:16 ` Stefan Beller
2014-12-30 20:31 ` Junio C Hamano
2014-12-30 20:47 ` Junio C Hamano [this message]
2014-12-30 20:52 ` Michael Haggerty
2014-12-30 20:55 ` Junio C Hamano
2014-12-30 21:39 ` Robert Dailey
2014-12-31 1:26 ` Jeff King
2014-12-30 21:49 ` Michael Haggerty
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=xmqq1tngsw55.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=rcdailey.lists@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.