npub1cj…m4kmd on Nostr: npub1upkp7…4tcwy > Git doesn’t have any built in mechanisms to track how recently ...
npub1upkp7fd7rc3lrjg23r8gy0wc723vze7mxlx5984ut6zurjzpf5xss4tcwy (npub1upk…tcwy)
> Git doesn’t have any built in mechanisms to track how recently you fetched
The reflog does keep dates! But,
1 — you have to ask for them:
¶ git reflog --date=human
Then instead of HEAD@{1} etc, you get HEAD@{time}
2 — By default, `git reflog' shows you the reflog of HEAD, but git keeps other reflogs, so you can see fetches of a remote-tracking branch which you did not check out.
¶ git reflog origin/main --date=human
or,
¶ git reflog --all --date=human
> Git doesn’t have any built in mechanisms to track how recently you fetched
The reflog does keep dates! But,
1 — you have to ask for them:
¶ git reflog --date=human
Then instead of HEAD@{1} etc, you get HEAD@{time}
2 — By default, `git reflog' shows you the reflog of HEAD, but git keeps other reflogs, so you can see fetches of a remote-tracking branch which you did not check out.
¶ git reflog origin/main --date=human
or,
¶ git reflog --all --date=human