Re: [PATCH] --walk-reflogs: actually find the right commit by date.

Johannes Schindelin [off-list ref] writes:

Embarassing thinko.

Aha, progress ;-).  But it still seems to pick up entry that is
less than specified number of hours if I do:

	$ git log --walk-reflogs -4 master@{1.hour} | head -2
        commit 33dd19c2a9c0b114436f53d86fc1c2c5e00c26bb
        Reflog: master@{Sat, 20 Jan 2007 00:01:35 -0800} (Junio C Ham

It is Jan 20th 02:10 now and the master was not pointing at that
commit 1 hour ago.

Anyway, I am done for the night -- I haven't finished testing
the updated 'master' and 'next', so I'll push out the tip of
'pu' (which contains all of the tentitive 'master' and 'next'
changes I haven't verified yet) and call it a day.

Hi,

On Sat, 20 Jan 2007, Junio C Hamano wrote:

Johannes Schindelin [off-list ref] writes:

quoted

Embarassing thinko.

Aha, progress ;-).  But it still seems to pick up entry that is
less than specified number of hours if I do:

	$ git log --walk-reflogs -4 master@{1.hour} | head -2
        commit 33dd19c2a9c0b114436f53d86fc1c2c5e00c26bb
        Reflog: master@{Sat, 20 Jan 2007 00:01:35 -0800} (Junio C Ham

It is Jan 20th 02:10 now and the master was not pointing at that
commit 1 hour ago.

I tried to reproduce this effect, but so far no luck. I even let the 
function get_reflog_recno_by_time() output what it does, and it picks 
exactly the right commit. Do you have a time skew?

Ciao,
Dscho