From: Jeff King <peff@peff.net>
To: Craig H Maynard <chmaynard@me.com>
Cc: git@vger.kernel.org
Subject: Re: git reflog --date
Date: Wed, 12 Aug 2020 05:14:36 -0400 [thread overview]
Message-ID: <20200812091436.GA18444@coredump.intra.peff.net> (raw)
In-Reply-To: <730B4EB4-AA72-4097-9487-D6B8623BB8E5@me.com>
On Tue, Aug 11, 2020 at 08:28:55PM -0400, Craig H Maynard wrote:
> I'm using git version 2.28.0. I don't see any mention of this 'git reflog' option in the online Git docs:
>
> git reflog --date=iso
>
> Any I missing something?
The reflog command defaults to "reflog show" if no command is given
(from the "Description" section of "git help reflog"):
The "show" subcommand (which is also the default, in the absence of
any subcommands) shows the log of the reference provided in the
command-line (or HEAD, by default). The reflog covers all recent
actions, and in addition the HEAD reflog records branch switching. git
reflog show is an alias for git log -g --abbrev-commit
--pretty=oneline; see git-log(1) for more information.
And the implication that it takes the same options as git-log is spelled
out explicitly in the Options section:
Options for show
git reflog show accepts any of the options accepted by git log.
You can find a more detailed description of --date in the git-log
manpage.
-Peff
next prev parent reply other threads:[~2020-08-12 9:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-12 0:28 git reflog --date Craig H Maynard
2020-08-12 9:14 ` Jeff King [this message]
2020-08-12 12:34 ` Craig H Maynard
-- strict thread matches above, loose matches on Subject: below --
2014-10-21 8:11 John Tapsell
2014-10-21 17:24 ` Junio C Hamano
2014-10-21 17:31 ` John Tapsell
2014-10-21 18:06 ` Junio C Hamano
2014-10-21 18:12 ` John Tapsell
2014-10-21 23:11 ` Junio C Hamano
2014-10-21 22:21 ` Junio C Hamano
2014-11-04 17:06 ` Phil Hord
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200812091436.GA18444@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=chmaynard@me.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).