From: Michael Haggerty <mhagger@alum.mit.edu>
To: Junio C Hamano <gitster@pobox.com>
Cc: Robert Dailey <rcdailey.lists@gmail.com>, Git <git@vger.kernel.org>
Subject: Re: Why do dates in refspecs require the reflog?
Date: Tue, 30 Dec 2014 22:49:31 +0100 [thread overview]
Message-ID: <54A31DEB.7020900@alum.mit.edu> (raw)
In-Reply-To: <xmqqppb0rh63.fsf@gitster.dls.corp.google.com>
On 12/30/2014 09:55 PM, Junio C Hamano wrote:
> Michael Haggerty <mhagger@alum.mit.edu> writes:
>
>> There is yet a third similar question: "What is the last commit that is
>> currently on the master branch that was *authored* at least one year
>> ago? Please note that this question is even subtler, because author
>> timestamps are often out-of-order even on a single branch (whereas
>> commit timestamps are usually in order). I don't know of a simple git
>> command to answer this question.
>
> --author-date-order?
Does --author-date-order cause --before/--after/--since/--until to use
author dates rather than commit dates? The documentation doesn't mention
that effect. If not, then it doesn't help much.
Michael
--
Michael Haggerty
mhagger@alum.mit.edu
prev parent reply other threads:[~2014-12-30 21:49 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
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 [this message]
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=54A31DEB.7020900@alum.mit.edu \
--to=mhagger@alum.mit.edu \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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 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).