[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [DESIGN] mtime versioning - was: Getting Bug 1256 fixed

From: Ph. Marek <philipp.marek_at_bmlv.gv.at>
Date: 2005-11-28 13:35:12 CET

On Monday 28 November 2005 13:11, Giovanni Bajo wrote:
> It's not clear to me whether "svn up -rN" should restore the modification
> time of the files at that revision. If so, that would break a common usage
> pattern such as:
> I took some time to search the archive for previous discussions about mtime
> versioning. After some reading, the only argument that convinced me is that
> of importing external trees.
And every other usage which does not involve make, eg. documents.

> In my mind, it would be "svn import" *only* to
> remeber the mtime of the files being imported (at least by default), so
> that it can be restored later. I still fail to see what's good in having
> "svn commit" records and stores the mtime of each and every file.
That's why my patch only stores for files _with svn:text-time set_. All others
are treated as before.

> Off the
> top of my head, you will also have to fight endless trouble with timezones,
> DST, different time encoding in Windows and UNIX, and whatnot.
If you take a look into the stored timestamps you'll see that they look like
i.e. are stored in a text-format, UTC. Resolution up to microseconds, all
conversions are done by svn. Which trouble could there be?



To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Nov 28 13:37:22 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.