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

Re: Automatic pretty-print

From: Zeus G├│mez Marmolejo <zeus22_at_casal.upc.es>
Date: 2004-08-18 20:59:21 CEST

Quoting Ben Collins-Sussman <sussman@collab.net>:

> On Wed, 2004-08-18 at 12:36, Zeus G├│mez Marmolejo wrote:
>
>> The ideal think could be at the pre-commit hook execute the pretty
>> printer for
>> all the .c source files so that in the repository the files all are well
>> stored. Also it would be desirable to check C syntax so all files
>> that are in
>> the repository complile all. But I've seen the comments on the pre-commit
>> template hook and explicitly reports that the script must not change the
>> transaction. So is there a way to transform (pretty-print) the source files
>> before committing them?
>
> Yes, make your users do it. :-)
>

Well, the problem is there are a lot of programmers and I can not enforce to
all of them to execute the pretty-printer before commiting. It must be done
transparently to the programmer. And also when the commit is done it would be
very good that the svn 'returns' the correct pretty-printed version to the
committer and substitutes the bad one at commit time.

> Have the pre-commit hook run some sort of 'validation' on the syntax of
> incoming changes. If they're badly formatted, reject the commit. This
> forces users to write nicely formatted code, or run a transformation
> program before committing.

How can I run this transformation program before commiting, is there any way!?
I think in the pre-commit hook I can not modify the transaction, but what
happens if I do it??

Zeus.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Aug 18 21:00:13 2004

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