Re: $log a new angle!

On 11/13/07, Jon Hardcastle <jd_hardcastle@yahoo.com> wrote:
> I appreciate this is going to attract the scorn of
> many, but i have to ask.
No scorn, just sympathy for your situation.

[...]
> Basically one of the files goes to the client, and
> they want the file history present in the file.
>
> I am currently considering using the pre-commit hook,

As stated by other, very BAD thing to do. Even using a client side
hook is a poor idea.

> but I am very open to suggestions? It boils down to
> the fact they have not long ago rolled this
> functionality out much to the collective Horrahs! from
> the clients. They don't now want to change it for risk
> of egg on faceage.
>
> Heeelp!

Your best option would be to have a delivery script (probably part of
your release process) that will scan for the $log$ keyword, fetch the
log entries for that file (using "svn log"), then insert them into the
copy for delivery.

This will mean that the working (and repository) copies of the file(s)
will have just the unexpanded $log$, but this is both much safer and
much cleaner.

This would probably be less than 10 lines of Perl to do.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Wed Nov 14 19:31:27 2007