On Mar 11, 2006, at 16:35, Jan Warnking wrote:
>> - a bigger annoyance is the algorithm used for checking whether a
>> property has been modified with a propedit command. If I do:
>> svn propedit myproperty --editor-cmd "sed -i -e 's/foo/bar/g'" mypath
>> then svn will respond: "No changes to property 'myproperty' on
>> 'mypath'". This occurs because SVN checks the timestamp
>> (modification time) and file size of the temporary file containing
>> the property value, in order to determine whether a change
>> occurred. Sed is fast enough so that the modification time appears
>> unchanged, and the replacement done does not change file length.
>> Of course I can change this command to:
>> svn propedit myproperty --editor-cmd "sleep 2; sed -i -e 's/foo/
>> bar/g'" mypath
>> That works, but is slow. The whole point of scripting is that I
>> have potentially many files to process.
> Thanks, Marc, for the hint on tail +... . On the issue with svn
> propedit being unusable in scripts I gave up and am using a
> combination of propdel and propset now. Quite ugly but it works.
> I'd still like to hear if this is someting that has come up before
> and if there are plans to fix it.
The fact that Subversion doesn't notice differences if the
modification occurs within the same second has come up on the list
before. For example:
http://svn.haxx.se/users/archive-2005-03/0783.shtml
I searched http://svn.haxx.se/users for "one second"; there were
other results.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Mar 11 17:52:06 2006