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

RE: Post Commit Code Formatting

From: Servico Tpd Rodrigo Alfonso Menezes Madera <tpd.madera_at_telefonica.com.br>
Date: 2005-06-22 21:33:25 CEST

Hey, nice idea, so this solution would make an _additional_ commit when
someone commits. Thatīs two commits per commit =o)

Combining this idea of yours to the previous idea of checking if the files
are already processed we can make this second commit optional.

Iīm starting to like this!

Rodrigo

> -----Original Message-----
> From: Durfee, Bernard [mailto:Bernard.Durfee@suny.edu]
> Sent: 22. juni 2005 20:15
> To: users@subversion.tigris.org
> Subject: RE: Post Commit Code Formatting
>
> Again, it seems like it would very simple for CVS/Subversion to supply a
> 'hook' for people to run scripts to modify incoming files and transmit
> those modifications back to the client, just as both of those systems
> already do with keyword expansion.
>
> Bernie

You don't need a special hook for this.

1. In a post-commit hook, put a job in some queue.
2. Have a service process the jobs in the queue. Checkout the branch that
was changed, format the changed files, and commit.

You have to lock the changed files and verify in a pre-commit hook that a
locked file is not committed to (to avoid merge conflicts).

Casper

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jun 22 21:33:06 2005

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