views:

38

answers:

1

It might sound unnecessary, but let me explain my problem first. Probably then it would make sense.

Few artists keep updating images based on clients' change requests. An artist makes changes accordingly and commits with proper 'commit messages'. Just before actual commit, I want to create a text file with image properties like size and all the 'commit messages'. And then this file would be committed itself. So basically some sort of pre-commit processing is required. Even though most of the artists are not very comfortable with svn, they can always see what changes were made last time to the image via simple text file. So artists only do update and commit with svn.

How this could be done?

Are there any better alternatives?

+3  A: 

This could probably be done with hooks etc. as you say. I would go the other way and provide a script/program/webpage that extracts information from the commit log and displays it when required, as a kind of user friendly wrapper around svn log.

calmh