Re: Bug with revisions?

Wouldn't it be safer to hash the size & timestamp and use that instead?
I don't think that would affect performance significantly considering
both filesize and timestamp come from the inode.. but then this is
hardly my area of expertise..

        
It just strikes me as incredibly unsafe to rely on timestamp alone..
particularly for diff output! Perhaps at least provide an option to
force a diff even if the timestamp is the same? Just for those few
times when we do something that's scripted...

k.

On Thu, 2004-07-15 at 15:16, C. Michael Pilato wrote:
> Kasia Trapszo <ktrapszo@tickets.com> writes:
>
> > I'm not mocking with timestamps.. this was something that was scripted
> > and while unlikely, I suppose my script was fast enough to write two
> > version of a file within the same second.. you are looking at the
> > timestamp up to the second, right?
>
> Last I knew, Subversion was supposed to sleep() for a second in
> relevant situations so that this exact problem would be avoided (so
> long as the Subversion process wasn't backgrounded, I suppose).

-- 
Kasia Trapszo <ktrapszo@tickets.com> 
Software Engineer - Tickets.com
office: 203-741-3028      cell: 860-916-8179
aim: kasiachick            yim: kasiachick
     Telepathy available upon request
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org