[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
UCE Complaint (Re: applying astyle on commit)
From: |
Christopher Fogarty |
Subject: |
UCE Complaint (Re: applying astyle on commit) |
Date: |
Thu, 19 Apr 2001 14:59:49 -0400 |
You have sent the attached unsolicited e-mail to my
e-mail account.
I do not wish to receive such messages in the future.
Please remove my name from your lists immediately.
--- This message was intercepted by SpamKiller (www.spamkiller.com) ---
[ On Thursday, April 19, 2001 at 18:47:33 (+0200), Maarten de Boer wrote: ]
> Subject: applying astyle on commit
>
> So my question is: how can I do this? Doing it client
> side is not really an option, because we use different
> platforms, and besides, doing it server-side assures
> correct usage of astyle.
Generally speaking that's way outside the scope of any pure versioning
tool. Something like style enforcement is more along the lines of
automated policy enforcment in a larger process model. Remember:
CVS is not an automated testing program.
CVS does not have a builtin process model.
If I were you I would switch to using Aegis -- it offers a two-phase
commit policy and also offers the ability to require a series of tests
to complete on all commits. With Aegis you could arrange things in such
a way that one of the tests was a style conformance test or you could
do style conformance tests as part of the second commit phase and push
any non-conforming changes back to the developer for correction.
--
Greg A. Woods
+1 416 218-0098 VE3TCP <address@hidden> <address@hidden>
Planix, Inc. <address@hidden>; Secrets of the Weird <address@hidden>
_______________________________________________
Info-cvs mailing list
address@hidden
http://mail.gnu.org/mailman/listinfo/info-cvs
- UCE Complaint (Re: applying astyle on commit),
Christopher Fogarty <=