Thread (1 message) 1 message, 1 author, 2016-06-15
  • (off-list ancestor, not in this archive)
  • Re: git reflog --date · Junio C Hamano <hidden> · 2016-06-15

Re: git reflog --date

From: Junio C Hamano <hidden>
Date: 2016-06-15 23:02:46

Junio C Hamano [off-list ref] writes:
John Tapsell [off-list ref] writes:
quoted
For me, writing "git reflog @{now}"  is a lot less intuitive than "git
reflog --date"

Currently the top google search for this question is here:

http://stackoverflow.com/questions/17369254/is-there-a-way-to-cause-git-reflog-to-show-a-date-alongside-each-entry

Which doesn't mention "@{now}"   at all.
I would say that a site where cluelesses attempt to lead other
cluelesses is not the best source of information ;-), but that tells
us that either our docs are not read by people or they do not give
necessary information to them clearly enough.
And it turns out it is a little bit of both.  We have this shown in
"git log --help":

    -g::
    --walk-reflogs::
    ...
    By default, 'commit@\{Nth}' notation is
    used in the output.  When the starting commit is specified as
    'commit@\{now}', output also uses 'commit@\{timestamp}' notation
    instead.

and "git reflog --help" says that "It is an alias for git log -g
--abbrev-commit --pretty=oneline; see git-log(1)." in fairly early
part of its description.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help