Zsh Mailing List Archive
Messages sorted by:
Re: sourceforge.net CVS tree ready for use
- X-seq: zsh-workers 10395
- From: Adam Spiers <adam@xxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxxxxxx
- Subject: Re: sourceforge.net CVS tree ready for use
- Date: Sun, 2 Apr 2000 23:02:49 +0100
- In-reply-to: <slrn8edoj0.ft8.mason@xxxxxxxxxxxxxxxxxxxxx>; from mason@xxxxxxxxxxxxxxx on Sun, Apr 02, 2000 at 06:02:08AM +0000
- Mail-followup-to: zsh-workers@xxxxxxxxxxxxxx
- Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
- References: <20000402014540.D22212@xxxxxxxxxxxxxxxxxxxxxxx> <1000402043752.ZM17756@xxxxxxxxxxxxxxxxxxxxxxx> <slrn8edoj0.ft8.mason@xxxxxxxxxxxxxxxxxxxxx>
- Reply-to: Adam Spiers <adam@xxxxxxxxxx>
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.)
> :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: