[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-19 13:08:15 CEST

Quoting Tom Mornini <tmornini@infomania.com>:

> Hash: SHA1
> Hash: SHA1
> Hash: SHA1
> On Aug 18, 2004, at 8:57 PM, Zeus Gómez Marmolejo wrote:
>> We all are agree with this style but I think is to painful to impose the
>> programmers to do the pretty-print in each commit. I think for me this tool
>> (Subversion) is very good but it's missing some functionality. The
>> restriction for the pre-commit hooks not to modify the data is too strict. I
>> think for future releases, subversion could accept the modifications in the
>> pre-commit hooks, syncronize the commiter with these changes and insert the
>> new revision in the database.
> Wrap svn commit in a simple script that does:
> 1) crawl through current directory and children
> 2) pretty print .c files
> 3) svn commit

OK, this option is much like what I want. But, I can wrap the server command:
svnserve? Or it's done in the clients? If it's done in the clients we have
the same problem as before. If I can wrap the server command 'svnserve' to
check the .c files first and then do the real 'svn commit' is fine for me.

Another thing that I'm thinking about, related to what Erik suggested, is to
checkout the repository at midnight in the server as a cron task, run the
pretty-printer software and if the result is different from what it's in the
server, commit a new revision each day.

> Why, oh, why...would you argue with people who wrote the tool and
> suggest
> they're wrong about the tool itself.

I'm completely agree with developers, but I don't understand how you don't
accept that the software might do this new thing. What I'm proposing is a
different functionality that the tool doesn't have: the possibility of
changing the transaction in pre-commit time. I think it's worth mentioning
it. May be this situation will happen again in the near future but not with

> They told you a few times that the working copy MUST match the
> repository,
> or everything will get messed up.
> - - - -- - -- Tom Mornini
> - - -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (Darwin)
> iD8DBQFBJB88zaKkuvKwKvcRAi4UAJ93r8IYfTH6FxVsHV2DJxsaibaIIgCfeuPJ
> 09kkh9woXW0F3i04CMvSuVw=
> =WInr
> - - -----END PGP SIGNATURE-----
> - - -- - -- Tom Mornini
> Version: GnuPG v1.2.4 (Darwin)
> iD8DBQFBJB9DzaKkuvKwKvcRAj1EAKCIM5o9dwB/7flNYcLz6NYb5FT4dQCgiSr0
> LhwCJEIboJl7rGsvhsb1KbI=
> =Cl2t
> - -----END PGP SIGNATURE-----
> - --
> - -- Tom Mornini
> Version: GnuPG v1.2.4 (Darwin)
> N+IwHZbPspjVLbJH/Qqmj1M=
> =Aakq

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Aug 19 13:12:12 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.