> On Sun, Aug 21, 2011 at 07:21, Andy Canfield <andy.canfi...@pimco.mobi> wrote: >> I created a repository and created a subdirectory in it named 'scripts'. In >> this are a half-dozen Linux shell scripts. Unfortunately, I set the execute >> flag on only five of them; the sixth was untested as of my first commit so I >> had never noticed that the execute attribute was unset. >> >> [1] I set the execute attribute and did a commit, but the file was not >> updated in the repository. Apparently the change in atributes was not >> recognized as a file change by Subversion.
On Sun, Aug 21, 2011 at 7:48 AM, Andy Levy <andy.l...@gmail.com> wrote: > If the file's timestamp didn't change, Subversion won't pick up the change. If you change a property on the file, the file's timestamp doesn't change, but Subversion does pick up the change. Subversion works on the file's timestamp and the timestamp in the .svn directory of the files that represent the file. If you edit a file, and change its timestamp, it alerts Subversion that a file has possibly been changed and is compared to the base stored in the .svn directory. If you edit a property, the timestamp in the .svn directory was changed. Some of this may change in Subversion 1.7 since each directory doesn't have a .svn directory in it. -- David Weintraub qazw...@gmail.com
