2008/7/10 ¹ùìÏ <guoy_at_dscomm.com.cn>:
> Dear Invendor,
>
> This is a software company in china. I'm an engineer at
> develope-management department.
>
> We used other version control system as perforce or starteam before.
> Now we are trying subversion.
>
> During trying subversion, we find that file modify time could not be
> saved into subversion and get from subversion.
>
> Is it a design problem or deploy problem ? I hope it's a deploy
> problem. How to shot it, if a deploy problem.
>
There is a configuration option "use-commit-times" which you can find
in the documentation, It does not preserve the real file modify time
but the commit time which might be good enough.
However, for software development, the default behaviour (file time is
the time of last update or checkout) usually works best.
The problem with preserving file modify time is that it is very hard
to do right. What is the correct modify time if two people change the
same file and then they commit/update/merge the data? What to do when
merging a branch? IF SVN modifies the file contents during a commit
(see svn:keyword property) does that count as a file modification or
not?
Norbert
Received on 2008-07-10 23:07:07 CEST