On 8/31/2010 11:22 AM, Tech Geek wrote:
> >You want to enforce that the developer cannot commit unless they have
> this project.xml in >their working copy, though it will never be sent to
> the repository.
> That's not true. The project.xml (or whatever file that particular file
> is) should also be a part of commit.
>
> I will again repeat my question again since there is so much confusion:
>
> Can we have a pre-commit (preferred) or post-commit server hook that can
> check for the presence of a particular file (say project.xml) when the
> users send their working copy to the server to commit? If the file is
> present accept the commit (along with that file) else reject the commit.
>
> I would prefer not to implement this on client side.
>
> I never thought this would be so complicated.
I'm still confused. Is it a requirement that the file be changed each
time (and thus part of a commit), or just that it exists somewhere on
the client side (versioned or unversioned)? The server will only know
about it when it changes since the svn client is smart enough to only
send differences.
--
Les Mikesell
lesmikesell_at_gmail.com
Received on 2010-08-31 18:36:16 CEST