Reid Priedhorsky wrote:
> Ryan Schmidt wrote:
>> On Sep 7, 2006, at 19:28, Reid Priedhorsky wrote:
>>
>>> I'm storing TeX documents in my Subversion repository, and I also
>>> store the corresponding PDFs, because some people who use the
>>> repository don't have the tools to generate them.
>>>
>>> However, I occasionally leave the PDF out of date in a commit.
>>>
>>> Therefore, I would like to write a pre-commit hook that prevents me
>>> from doing this. The rule would be, if a .tex file is being
>>> committed, and a corresponding .pdf file is also being committed,
>>> and the .tex is newer than the .pdf, reject the commit.
>>>
>>> However, I can't figure out how to look at the last-modified
>>> timestamps of the files being committed.
>>
>>
>> In the pre-commit hook you would use the svnlook command to examine
>> the transaction that's in progress. svnlook has many subcommands
>> including getting a list of files in the transaction and getting a
>> file's properties, including its date.
>
> I found plenty of information on finding which files were in the commit,
> and the timestamp of the commit (both using svnlook), but I couldn't
> locate info on last-modified timestamps of individual files in the
> commit. Could you give a more specific pointer into the documentation?
The Subversion client doesn't send the file's last modified time to the server.
Your best bet in this case is to do the test, if there's a commit to any of the
.tex files, then the .pdf file must also be in the commit.
Regards,
Blair
--
Blair Zajac, Ph.D.
<blair@orcaware.com>
Subversion training, consulting and support
http://www.orcaware.com/svn/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Sep 8 04:16:05 2006