{"thread":{"id":"41509","subject":"reflog: weird options","startedAt":"2016-02-25T00:00:33Z","lastAt":"2016-02-25T00:49:11Z","messageCount":2,"participants":["David Turner","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"279235","messageId":"1456358433.18017.35.camel@twopensource.com","threadId":"41509","inReplyTo":null,"subject":"reflog: weird options","fromName":"David Turner","fromEmail":"dturner@twopensource.com","sentAt":"2016-02-25T00:00:33Z","receivedAt":"2016-02-25T00:00:33Z","isPatch":false,"sender":{"key":"novalis@novalis.org","avatar":"https://avatars.githubusercontent.com/u/77003?v=4"},"body":"The manual for git reflog says it takes \"[log-options]\".  And it does,\nsort-of.  For instance, you can give a path, and it will only show you\nreflog entries that touch that path (I'm not sure why you would want to\ndo that, but you can!).  But you can also give --merges, which will\nsilently give you no reflog entries.  I don't know why.\n\nOne useful option that may or may not exist: show the time the reflog\nentry was made.  I'd really like to say, \"well, I know it was working\nas-of last Tuesday...\".  I know the data is in the reflog, but I don't\nknow how to show it.  I can show the committer date, which is usually\ngood enough when I'm rewriting a patch series, but that is not quite\nthe same thing.\n \nI know I could fix these issues, but unfortunately I don't have the\ntime right now. It might make a good starter project for someone new to\ngit development!\n"},{"id":"279244","messageId":"xmqqbn75r4vs.fsf@gitster.mtv.corp.google.com","threadId":"41509","inReplyTo":"1456358433.18017.35.camel@twopensource.com","subject":"Re: reflog: weird options","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2016-02-25T00:49:11Z","receivedAt":"2016-02-25T00:49:11Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"David Turner <dturner@twopensource.com> writes:\n\n> The manual for git reflog says it takes \"[log-options]\".  And it does,\n> sort-of.  For instance, you can give a path, and it will only show you\n> reflog entries that touch that path (I'm not sure why you would want to\n> do that, but you can!).  But you can also give --merges, which will\n> silently give you no reflog entries.  I don't know why.\n>\n> One useful option that may or may not exist: show the time the reflog\n> entry was made.  I'd really like to say, \"well, I know it was working\n> as-of last Tuesday...\".  I know the data is in the reflog, but I don't\n> know how to show it.  I can show the committer date, which is usually\n> good enough when I'm rewriting a patch series, but that is not quite\n> the same thing.\n>  \n> I know I could fix these issues, but unfortunately I don't have the\n> time right now. It might make a good starter project for someone new to\n> git development!\n\nI think somebody who is fairly new to the project was already\nlooking into it.  The hacky way the feature to show \"reflog\" entries\nwas implemented (i.e. done by tweawking the \"git log\" machinery,\neven though the entries that comes out of the \"log\" and \"reflog\" are\nquite different things, as you observed by the lack of \"time the\nreflog entry was created\") shows up as these inconsistencies and\n\"Huh?\"s.\n"}]}