Re: File timestamps?

2018-01-10 Thread Bo Berglund
On Wed, 10 Jan 2018 13:08:14 +0100, Johan Corveleyn
 wrote:

>On Wed, Jan 10, 2018 at 1:02 PM, Bo Berglund  wrote:
>> Is there some argument that can be applied to svn co to tell it to
>> keep the timestamps?
>
>There is a client-side configuration option for that: use-commit-times=true.
>See the "use-commit-times" option in this section of the book:
>http://svnbook.red-bean.com/nightly/en/svn.advanced.confarea.html#svn.advanced.confarea.opts.config

Thanks,
I enabled the setting in my Subversion\config file and did a new
checkout of a module. Now I am getting the repo timestamps!


-- 
Bo Berglund
Developer in Sweden



Re: File timestamps?

2018-01-10 Thread Johan Corveleyn
On Wed, Jan 10, 2018 at 1:02 PM, Bo Berglund  wrote:
> I notice that if I do a svn co on a project all files will get a
> timestamp as of the co time.
> But if I do a svn export of the same project the files retain their
> original timestamps (the time of commit of the file).
> Is there some argument that can be applied to svn co to tell it to
> keep the timestamps?

There is a client-side configuration option for that: use-commit-times=true.
See the "use-commit-times" option in this section of the book:
http://svnbook.red-bean.com/nightly/en/svn.advanced.confarea.html#svn.advanced.confarea.opts.config

-- 
Johan


File timestamps?

2018-01-10 Thread Bo Berglund
I notice that if I do a svn co on a project all files will get a
timestamp as of the co time.
But if I do a svn export of the same project the files retain their
original timestamps (the time of commit of the file).
Is there some argument that can be applied to svn co to tell it to
keep the timestamps?


-- 
Bo Berglund
Developer in Sweden



Re: Double update of versioned file externals corrupting file timestamps

2010-06-23 Thread Daniel Shahaf
Yes, thanks for asking, please link to the thread from the issue. 

Thanks,

Daniel

Franz Sirl wrote on Wed, 23 Jun 2010 at 10:52 -:
 Hi,
 
 anyone care to comment on this? Is this report OK to enter into the issue
 database?
 
 Franz
 
 
 Am 2010-06-14 10:55, schrieb Franz Sirl:
  Hi,
  
  we stumbled over an annoying issue with subversion 1.6.11. If we update
  a WC with versioned file externals, files where the version is not equal
  to the last revision of the file, are double-updated on _every_ update
  like this:
  
  [u...@machine:~/a/test_file_externals]$ svn up
  U trunk/combined-src/file1.c
  
  Fetching external item into 'trunk/combined-src/file1.c'
  U trunk/combined-src/file1.c
  Updated external to revision 4.
  
  
  Fetching external item into 'trunk/combined-src/file2.c'
  Updated external to revision 4.
  
  Updated to revision 6.
  [u...@machine:~/a/test_file_externals]$ svn up
  U trunk/combined-src/file1.c
  
  Fetching external item into 'trunk/combined-src/file1.c'
  U trunk/combined-src/file1.c
  Updated external to revision 4.
  
  
  Fetching external item into 'trunk/combined-src/file2.c'
  Updated external to revision 4.
  
  Updated to revision 6.
  [u...@machine:~/a/test_file_externals]$
  
  
  Naturally this updates the file timestamps everytime and thus triggers
  Makefile actions.
  
  Is this a known issue? Should I file a bug in the issue tracker? Find
  attached a FSFS based demo repository showing the bug.
  
  Franz
 
 
 


Double update of versioned file externals corrupting file timestamps

2010-06-14 Thread Franz Sirl

Hi,

we stumbled over an annoying issue with subversion 1.6.11. If we update 
a WC with versioned file externals, files where the version is not equal 
to the last revision of the file, are double-updated on _every_ update 
like this:


[u...@machine:~/a/test_file_externals]$ svn up
Utrunk/combined-src/file1.c

Fetching external item into 'trunk/combined-src/file1.c'
Utrunk/combined-src/file1.c
Updated external to revision 4.


Fetching external item into 'trunk/combined-src/file2.c'
Updated external to revision 4.

Updated to revision 6.
[u...@machine:~/a/test_file_externals]$ svn up
Utrunk/combined-src/file1.c

Fetching external item into 'trunk/combined-src/file1.c'
Utrunk/combined-src/file1.c
Updated external to revision 4.


Fetching external item into 'trunk/combined-src/file2.c'
Updated external to revision 4.

Updated to revision 6.
[u...@machine:~/a/test_file_externals]$


Naturally this updates the file timestamps everytime and thus triggers 
Makefile actions.


Is this a known issue? Should I file a bug in the issue tracker? Find 
attached a FSFS based demo repository showing the bug.


Franz


test_file_externals.tar.bz2
Description: Binary data