Re: FW: Import and Commit and file modification times

"Svante Seleborg" <svante@axantum.com> writes:

> What is "the new code" - are you referring to Ph. Mareks code,

Yes.

> or someone
> elses code that does implement some kind of time stamp preserveration? I
> haven't seen that code, and this discussion was initiated since apparently
> no design discussion had been undertaken on this issue.

There was some discussion, I asked some or all of these questions last
time it came up. I didn't always get answers :)

> My proposed design would indeed detect changes betwen the timestamp and the
> corresponding property, and would indeed allow a commit after a "touch".
> It's the whole point - file modification times are an integral part of what
> the repository should store and version. A hypothetical project where the
> only changes was a "touch" would generate a new version for each commit with
> a different timestamp.

So status will show some sort of "modified" indicator whenever the
filesystem timestamp and the property timestamp don't match?
Ph. Mareks code doesn't do that (as far as I know) but someone could
write such a system.

Does it show up as text modifed 'M ', property modifed ' M', or some
other timestamp modified indicator?

If the text is modified then the timestamp is probably changed, does
the timestamp modification still show up when the text modification
gets shown?

What happens if I modify the timestamp property so that it matches the
modifed filesystem timestamp. Does that show up as a property
modification? Does it also show up as a timestamp modification?

If the filesystem timestamp resolution match the timestamp property
due to resolution does that show up as a timestamp modification? Does
such a change get committed?

-- 
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org