From: David Turner <dturner@twopensource.com>
To: git mailing list <git@vger.kernel.org>
Subject: reflog: weird options
Date: Wed, 24 Feb 2016 19:00:33 -0500 [thread overview]
Message-ID: <1456358433.18017.35.camel@twopensource.com> (raw)
The manual for git reflog says it takes "[log-options]". And it does,
sort-of. For instance, you can give a path, and it will only show you
reflog entries that touch that path (I'm not sure why you would want to
do that, but you can!). But you can also give --merges, which will
silently give you no reflog entries. I don't know why.
One useful option that may or may not exist: show the time the reflog
entry was made. I'd really like to say, "well, I know it was working
as-of last Tuesday...". I know the data is in the reflog, but I don't
know how to show it. I can show the committer date, which is usually
good enough when I'm rewriting a patch series, but that is not quite
the same thing.
I know I could fix these issues, but unfortunately I don't have the
time right now. It might make a good starter project for someone new to
git development!
next reply other threads:[~2016-02-25 0:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 0:00 David Turner [this message]
2016-02-25 0:49 ` reflog: weird options 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=1456358433.18017.35.camel@twopensource.com \
--to=dturner@twopensource.com \
--cc=git@vger.kernel.org \
/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.