From: Jeff King <peff@peff.net>
To: Robert Dailey <rcdailey.lists@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Michael Haggerty <mhagger@alum.mit.edu>,
Git <git@vger.kernel.org>
Subject: Re: Why do dates in refspecs require the reflog?
Date: Tue, 30 Dec 2014 20:26:16 -0500 [thread overview]
Message-ID: <20141231012615.GA8852@peff.net> (raw)
In-Reply-To: <CAHd499Bt6_SOkj9Pp+GcLGnwDUR-pgr_YKt4yqZBAHjX+vkM8Q@mail.gmail.com>
On Tue, Dec 30, 2014 at 03:39:53PM -0600, Robert Dailey wrote:
> It also feels like there should be a
> shorthand for the `git log` usage in conjunction with `git show`... I
> could probably make an alias for it.
One thing I didn't see mentioned in this thread is that the question
"show me the commit closest to time X" does not have a single answer.
When there are branches, there may be many such answers, one for each
line of simultaneous development.
So people tend not to ask that question[1], and therefore nobody
bothered to make a convenient shorthand for it.
-Peff
[1] What do they ask instead? I find most of my older queries for
commits are satisfied following parent links from well-known points.
E.g., finding where topic X was merged, and then walking backwards
using "^2" to see the tip of the original topic.
If I am looking for information about a particular file about a year
ago, I often turn to "-S" or git-blame (actually, "tig blame" in my
case, which lets you walk backwards interactively).
But of course the exact query will depend on just what it is you
want to know. :)
next prev parent reply other threads:[~2014-12-31 1:26 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 [this message]
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=20141231012615.GA8852@peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mhagger@alum.mit.edu \
--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).