Zsh Mailing List Archive
Messages sorted by: Reverse Date, Date, Thread, Author

Re: sourceforge.net CVS tree ready for use



Geoff Wing (mason@xxxxxxxxxxxxxxx) wrote:
> Bart Schaefer <schaefer@xxxxxxxxxxxxxxxxxxxxxxx> typed:
> :On Apr 2,  1:45am, Adam Spiers wrote:
> :} Subject: Re: sourceforge.net CVS tree ready for use
> :} We set up automatic e-mail notification of any commits.  (This
> :} would be easy enough[0].)
> :I'm curious whether you've found a way to prevent the generation of
> :one message per subdirectory when a commit spans several subdirs.
> :CVS is rather insistent that every directory is a "module" ... and
> :given that there are 8 subdirectories under Completion alone, we
> :certainly don't want one mesage per directory per commit fired off
> :to zsh-workers (or even to some new zsh-cvs-commits list).

The program we use at work does cope with commits spanning multiple
subdirs, but I suspect this only happens when all files/dirs being
committed are mentioned on the command-line.

> Yes, I was about to request this.  Aggregation of commit messages which
> occur at the same time, plus or minus a few seconds (to account for
> directory spanning when people might use ! to CVS to reuse a log message),
> and with the same log info would be very nice.

Very nice, but probably very hard!

> Somewhere I've got a perl program to insert into CVSROOT/loginfo,
> though it depends on what we can run on their server.

We can put anything we want in our CVSROOT/loginfo, so I don't think
we're limited by sourceforge.



Messages sorted by: Reverse Date, Date, Thread, Author