From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10133 invoked from network); 4 Apr 2000 01:27:19 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 4 Apr 2000 01:27:19 -0000 Received: (qmail 29430 invoked by alias); 4 Apr 2000 01:27:13 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 10445 Received: (qmail 29410 invoked from network); 4 Apr 2000 01:27:12 -0000 To: zsh-workers@sunsite.auc.dk Path: mason From: mason@primenet.com.au (Geoff Wing) X-Newsgroups: lists.zsh.workers Subject: Re: sourceforge issues Date: 4 Apr 2000 01:27:07 GMT Organization: PrimeNet Computer Consultants Distribution: local Message-ID: References: Reply-To: mason@primenet.com.au NNTP-Posting-Host: coral.primenet.com.au X-Trace: coral.primenet.com.au 954811627 10124 203.43.15.2 (4 Apr 2000 01:27:07 GMT) X-Complaints-To: usenet@coral.primenet.com.au NNTP-Posting-Date: 4 Apr 2000 01:27:07 GMT User-Agent: slrn/0.9.6.2 (NetBSD) Peter Stephenson typed: :- Geoff, I agree the number of tags makes things difficult. I won't be : adding per-patch tags myself, though I can see the point of it since CVS : doesn't make it easy for you to regenerate a patch otherwise. It : would probably be good to remove the old ones, though it's quite useful : to be able to go straight to what a patch did. If you can see the cvs log information easily then you can just checkout the source at a certain date (either before or after the patch). Or if want something specific to a file or set of files, generate a ChangeLog with version numbers, e.g. using a fairly current version of rcs2log, then you can get the affected files by version number. Regards, -- Geoff Wing : Work URL: http://www.primenet.com.au/ Rxvt Stuff : Ego URL : http://pobox.com/~gcw/ Zsh Stuff : Phone : (Australia) 0413 431 874