Thread (1 message) 1 message, 1 author, 2022-07-12

Re: Why is reflog so obscure?

From: Sergey Organov <hidden>
Date: 2022-07-12 15:21:35

Junio C Hamano [off-list ref] writes:
Thomas Guyot [off-list ref] writes:
quoted
Thanks for clarifying that - I suspected it since we can do
<branch>@{<date>} although I didn't find any reference branch reflogs
in the documentation. I could've missed it... Is there a way to read a 
branch reflog?
    $ git reflog ;# lists entries of reflog of HEAD, starting at HEAD@{0}
    $ git reflog HEAD ;# same
    $ git reflog HEAD@{4} ;# same, starting at HEAD@{4}
    $ git reflog master ;# entries of reflog of "master"
    $ git reflog master@{0} ;# same
    $ git reflog master@{now} ;# same, show with timestamps
    $ git reflog master@{4.minutes} ;# same, starting at master@{4.minutes}

For the branch that is currently checked out, you can omit the name
when you use any of the @{...} notation, so 

    $ git reflog @{0}
    $ git reflog @{now}

are often the easiest ways to view what you did on the current
branch.
Very handy, thanks! Would be nice to have this in EXAMPLES section of
corresponding manual page.

Honestly, I tried (admittedly not very hard) to figure how to get dates
from "git reflog" a few times, but every time I gave up, so this (along
with the --dates option turning dates output on) is not very
discoverable.

-- 
Sergey Organov
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help