AFAIK the general approach is to code up a pre-commit hook and notify
the user if the commit does not meet your guidelines.
Think about it - if the commit hook modified the code in the repository
then it would also have to push those changes back to the client. Makes
for a potentially nasty situation for testing and debug.
Eric
> -----Original Message-----
> From: aldana [mailto:aldana_at_gmx.de]
> Sent: Monday, April 07, 2008 11:06 AM
> To: users_at_subversion.tigris.org
> Subject: content access in commit hooks?
>
>
> as far as i know it is not possible to get to the contents of
committed
> files
> being able to change them. this way you could enforce code conventions
in
> terms of code-formatting and members-order.
>
> why does subversion not support this, maybe this could be a feature
for
> next
> releases?
>
> -----
> manuel aldana
> aldana((at))gmx.de
> homepage: http://www.aldana-online.de
> --
> View this message in context: http://www.nabble.com/content-access-in-
> commit-hooks--tp16537554p16537554.html
> Sent from the Subversion Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
> For additional commands, e-mail: users-help_at_subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-04-07 19:43:28 CEST