git/list[1] front-page[2] threads[3] people[4] search[5] about
 

reflog: weird options

From
David Turner <dturner@twopensource.com>
Date
Feb 25, 2016, 00:00 UTC
Message-ID
<1456358433.18017.35.camel@twopensource.com>

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: Junio C Hamano
Message 1 of 2 in “reflog: weird options”
  1. David TurnerFeb 25, 2016
  2. Junio C HamanoFeb 25, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.