Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: sourceforge.net CVS tree ready for use
- X-seq: zsh-workers 10384
- From: mason@xxxxxxxxxxxxxxx (Geoff Wing)
- To: zsh-workers@xxxxxxxxxxxxxx
- Subject: Re: sourceforge.net CVS tree ready for use
- Date: 2 Apr 2000 06:02:08 GMT
- Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
- Organization: PrimeNet Computer Consultants
- References: <20000402014540.D22212@xxxxxxxxxxxxxxxxxxxxxxx> <1000402043752.ZM17756@xxxxxxxxxxxxxxxxxxxxxxx>
- Reply-to: mason@xxxxxxxxxxxxxxx
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).
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. Somewhere I've got a perl
program to insert into CVSROOT/loginfo, though it depends on what we can
run on their server. Otherwise some external aggregator should/could be
set up.
Regards,
--
Geoff Wing : <gcw@xxxxxxxxx> Work URL: http://www.primenet.com.au/
Rxvt Stuff : <gcw@xxxxxxxx> Ego URL : http://pobox.com/~gcw/
Zsh Stuff : <gcw@xxxxxxx> Phone : (Australia) 0413 431 874
Messages sorted by:
Reverse Date,
Date,
Thread,
Author