On Wed, Nov 09, 2011 at 11:48:58PM -0800, Eric Raible wrote: > > But it may also be a misfeature, because it's not clear what you're > > actually trying to limit by. We have commit timestamps, of course, but > > when we are walking reflogs, we also have reflog timestamps. Did you > > actually want to say "show me all commits in the reflog, in reverse > > reflog order, omitting commits that happened before time t"? Or did you > > really mean "show me the reflog entries that happened before time t, > > regardless of their commit timestamp"? > > I meant "show me the reflog entries that happened *since* time t, > regardless of their commit timestamp. Err, yeah, sorry. Somehow in the middle of writing the email I got turned backwards about which direction we were interested in. But I think you get the point. > Since -g is asking specifying for the reflog, and since the reflog has > its own timestamps, I would expect that those timestamps be used. Then I think my one-liner patch should do what you want. And now it's not just anecdotal evidence that I think it's the right behavior. There are two of us; we're _data_. -Peff -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html