[Pkg-ossim-devel] Things todo for Pkg-OSSIM (CVS)

[Jeremy T. Bouse]

    That does sound about how I do it here on my private CVS server as
well as over on SourceForge. I have a perl script that gets ran on
commit. Along with sending out the email it also does permission
checking to make sure that a given developer has access to commit to a
given directory.

    Sorry I've been incommunicado... I've been re-installing my mail
servers to help improve performance as well as cut the amount of spam
and bounce notices I was getting. Everything should be back online now.

    I am planning that the next upload of any packages I have that are
listed under OSSIM I'll change the maintainer to the list address and
ensure the three of us are listed as uploaders. Since all this has
started I've contemplated creating something for Firewall Builder or
including it in OSSIM.

    Regards,
    Jeremy

David Gil wrote:

>El vie, 04-11-2005 a las 11:11 +0100, Javier Fernández-Sanguino Peña
>escribió:
>  
>
>>Yes, that could be done, but it'll take me a while to set it up.
>>    
>>
>
>I've just read this at planet.debian.net:
>
>Junichi Uekawa
>cvs-commitinfo for cvs on alioth.
>After searching and googling and testing, I finally figured out how to
>do CVS log message mails.In commitinfo file, add a line
>withDEFAULT /usr/bin/cvs-mailcommit --mailto mail-address --from
>mail-address --diff --full --root %r --dir %p %{sVv}.There are many
>different ways to write it, but most examples on the web were wrong,
>since apparently --cvs option no longer works with newer cvs releases.
>
>
>  
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Pkg-ossim-devel mailing list
>Pkg-ossim-devel at lists.alioth.debian.org
>http://lists.alioth.debian.org/mailman/listinfo/pkg-ossim-devel
>  
>