From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15650 invoked from network); 2 Apr 2000 04:38:08 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 2 Apr 2000 04:38:08 -0000 Received: (qmail 28012 invoked by alias); 2 Apr 2000 04:37:59 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 10382 Received: (qmail 27998 invoked from network); 2 Apr 2000 04:37:58 -0000 From: "Bart Schaefer" Message-Id: <1000402043752.ZM17756@candle.brasslantern.com> Date: Sun, 2 Apr 2000 04:37:51 +0000 In-Reply-To: <20000402014540.D22212@thelonious.new.ox.ac.uk> Comments: In reply to Adam Spiers "Re: sourceforge.net CVS tree ready for use" (Apr 2, 1:45am) References: <20000401121150.A18158@thelonious.new.ox.ac.uk> <20000402014540.D22212@thelonious.new.ox.ac.uk> X-Mailer: Z-Mail (5.0.0 30July97) To: zsh workers mailing list Subject: Re: sourceforge.net CVS tree ready for use MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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). -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.brasslantern.com