From dev-return-68283-apmail-ant-dev-archive=ant.apache.org@ant.apache.org Fri Aug 05 12:31:17 2005 Return-Path: Delivered-To: apmail-ant-dev-archive@www.apache.org Received: (qmail 81658 invoked from network); 5 Aug 2005 12:31:17 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 5 Aug 2005 12:31:17 -0000 Received: (qmail 16905 invoked by uid 500); 5 Aug 2005 12:31:14 -0000 Delivered-To: apmail-ant-dev-archive@ant.apache.org Received: (qmail 16871 invoked by uid 500); 5 Aug 2005 12:31:14 -0000 Mailing-List: contact dev-help@ant.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list dev@ant.apache.org Received: (qmail 82756 invoked by uid 99); 5 Aug 2005 10:28:57 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Date: Fri, 05 Aug 2005 11:28:50 +0100 From: Christian Ashby To: Ant Developers List Subject: Re: [OT] Sorry for the spam... Message-ID: <41F52FB992FE8EC2B13561C5@[172.16.10.6]> In-Reply-To: <42F33F77.6020700@it.fts-vn.com> References: <42F33F77.6020700@it.fts-vn.com> X-Mailer: Mulberry/3.1.6 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: Yes X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N > I'm messing around with CVS and trying to discover the latest version of > a repo in CVS - any CVS guru's around who know is it possible? There is no concept of a repository version, only of the version associated with each file. You can check to see which files are changed from your current version with a standard CVS update, but not whether a repository as a whole is 'current' > You can do something similar with svn, but CVS has versions/file. If > that's the case I may have to keep a hash of file/version for each file, > and that sucks Why do you need a repository version? It's fairly standard CVS practice to use tagging for release versioning - is this what you requirement is? Christian Ashby Spiralinks, Inc. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For additional commands, e-mail: dev-help@ant.apache.org