Re: Commit hooks and control of bad development practices?

>I have several issues with the ID substitution.
>#1 Not all the files we have under revision control could be modified this
>way.

That's true, binary files can't do this.

>#2 As I mentioned in my initial post, I assume this means all files in the
>local working copy will need to be
> modofied on each update from the repository. I currently have 44,000
>files in my source tree. Ugly.

The keyword can be applied recursively, and the substitution is done
automatically on each update/commit. I find it to be a great way to know
what revision a file is regardless of whether one has access to a working
copy or the repository itself.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue May 25 23:56:07 2004