SVN has a pristine copy of the checked-out files along with the working copy.  
When you issue a commit, SVN compares the pristine and the local files and 
_only_ sends the diffs.  So the presence of any file doesn't automatically mean 
that it will be visible in the commit _unless_ it changes every time.

Hope this helps.

Cheers,
Jim

On Aug 31, 2010, at 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.

Reply via email to