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

Creating a list to track cvs changes

On Fri, 2004-06-04 at 19:41, Sergio Talens-Oliag wrote:
> El Fri, Jun 04, 2004 at 02:23:16PM +0200, Andreas Tille va escriure:
> > On Fri, 4 Jun 2004, Ben Armstrong wrote:
> > > If there's a way to be notified by email of cdd cvs changes, I'd like to
> > > do that for at least myself.  I guess I ought to look at Alioth's
> > > capabilities and see if that is one of them.
> > IMHO there is a big need for this feature.  I'm an CVS beginner but I have
> > hear about other projects who send CVS changes to a mailing list which
> > can be subscribed by interested parties.  We could set up an alioth list
> > for this purpose (or rather two list one for doc/common and one for
> > common (=the cdd tools) and later more if there is some common development).
>   I was going to do it, but I'm not registered as a developer.

I have added you.

>   I asked braindimg to do it on IRC, but after looking at it we saw that
>   if we create a mailing list on alioth it can't be deleted or renamed,
>   so we decided that asking here first was a better idea.
>   So, which list(s) should we use? I think that using only one called
>   *cdd-cvs* should be enough.

I agree.  That's a good name.  Are the other admins in agreement?

>   Once the list(s) are created we just need to upload a log script (i.
>   e., the one on /usr/share/doc/cvs/contrib/log.gz) and modify the
>   CVSROOT/loginfo file putting something like this at the end:
>     # Report all commits to the same address
>     ALL $CVSROOT/CVSROOT/log %s -f $CVSROOT/CVSROOT/commitlog -m cdd-cvs@lists.alioth.debian.org

Sounds good.

synrg at debian dot org

Attachment: signature.asc
Description: This is a digitally signed message part

Reply to: