[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: applying astyle on commit

From: Maarten de Boer
Subject: Re: applying astyle on commit
Date: Fri, 20 Apr 2001 17:47:01 +0200

David Fuller wrote:
> From cvs help:
> The commitinfo file defines programs to execute whenever cvs commit is
> about to execute.  These programs are used for pre-commit checking to
> verify that the modified, added and removed files are really ready to be
> committed.  This could be used, for instance, to verify that the changed
> files conform to to your site's standards for coding practice.

Ok, I have a script which I call from the commitinfo file, that applies
astyle. It works well in the sense that the code gets stored in the
repository nicely formatted, and when other users do an update, they get
that version indeed. 

The user that commited the file, still has the unformatted revision on
his machine, but doing a cvs update to get the formatted revision fails,
because cvs thinks that the commiting client has the actual revision,
which of course normally is true. Even a cvs diff doesn't work.

Is there a (server-side) way to force response to client-side update
requests? In other words, when the client does a cvs update, tell
it that the revision indeed changed? 

If not, the client has to commit, delete the local file, update...

Kind regards,


reply via email to

[Prev in Thread] Current Thread [Next in Thread]