info-cvs
[Top][All Lists]
Advanced

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

Re: UCE Complaint (Re: applying astyle on commit)


From: Harald Kucharek
Subject: Re: UCE Complaint (Re: applying astyle on commit)
Date: Fri, 20 Apr 2001 08:58:23 +0200

Eric Siegerman wrote:
> 
> Then may I suggest that you unsubscribe from address@hidden,
> and not spam all of *us* with these bounce messages (three of
> which have appeared in my inbox in the last half hour).
> 
> Thank you.

Yeah, it's annoying, but calm down. I guess the guy is a regular reader of 
info-cvs
and his spam filter was triggered by the first message with all the 
dollar-sign's in
the subject and decided that all further mail from info-cvs is from a spammer.
Outsmarted.

Harald



> 
> On Thu, Apr 19, 2001 at 02:59:49PM -0400, Christopher Fogarty wrote:
> > 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
> >
> >
> >
> > _______________________________________________
> > Info-cvs mailing list
> > address@hidden
> > http://mail.gnu.org/mailman/listinfo/info-cvs
> --
> 
> |  | /\
> |-_|/  >   Eric Siegerman, Toronto, Ont.        address@hidden
> |  |  /
> With sufficient thrust, pigs fly just fine. However, this is not
> necessarily a good idea.
>         - RFC 1925 (quoting an unnamed source)
> 
> _______________________________________________
> Info-cvs mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/info-cvs

-- 
 iXpoint Informationssysteme GmbH #
           Daimlerstr. 3          # Harald Kucharek
          76275 Ettlingen         # address@hidden
    Tel/Fax +49 7243 3775-0/77    # www.ixpoint.de



reply via email to

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