[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Pre-commit transaction modification question

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2004-02-12 00:20:55 CET

On Wed, 2004-02-11 at 17:18, Brett Wooldridge wrote:

> Any help, pointers, and advice is appreciated.

DON'T DO IT.

If the repository mangles the files as they enter the repository, then
your working copy will be completely wrong. The working copy will
think, "ah, this file I committed is what the latest version looks
like", but in reality, the latest version in the repository is very
different. There's no way for the pre-commit hook to tell the working
copy that it mangled the data.

What Subversion people have done instead is to install a pre-commit hook
which merely *validates* a style, and rejects the whole commit if any
file files to conform. This forces users to run the reformatter.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Feb 12 00:25:20 2004

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.