This issue with this is that it creates additional revisions in the
repository. The expected behavior
by the user is that a diff between two subsequent versions will show
only the code that changed.
In the method below, the user needs to diff two versions back to
actually perform a semantic diff,
because the immediately prior version would just be the unformatted
file, not the real last revision.
bw
Szekeres Istvan wrote:
>This can also done automatically without any hooks. Just write a shell
>script that checks out the repository (or updates a working copy), checks the
>headers and updates them if necessary, then commits the changes.
>
>Of course this is not so real-time as the header updates done at commit
>time, but I think it is still acceptable.
>
>
>Istvan
>
>
>
>>As an example of the kinds of CVS hooks I've seen in the past at places
>>I've worked, and
>>an example of where such modification might be considered desirable by
>>SOME users: the
>>last place I worked was very concerned about proper legal notices
>>(headings) being in files.
>>The legal department saw fit to change what they wanted in those headers
>>on what seemed
>>like a release-by-release basis. A CVS hook (in perl) was written that
>>inserted the legal
>>notice at the head of every file; if the notice that was there didn't
>>match the new one, it was
>>replaced. This was done at checkin, transparently to the developer.
>>
>>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>For additional commands, e-mail: users-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Feb 13 18:44:01 2004