From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20919 invoked from network); 2 Apr 2000 14:06:35 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 2 Apr 2000 14:06:35 -0000 Received: (qmail 4294 invoked by alias); 2 Apr 2000 14:06:25 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 10389 Received: (qmail 4281 invoked from network); 2 Apr 2000 14:06:24 -0000 From: dmeyer@jhereg.penguinpowered.com Date: Sun, 2 Apr 2000 10:06:17 -0400 To: zsh-workers@sunsite.auc.dk Subject: sourceforge.net CVS tree ready for use Message-ID: <20000402100617.A1617@jhereg.dmeyer.org> Reply-To: dmeyer0@bellatlantic.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In article <000201bf9c8b$a6655830$21c9ca95@mow.siemens.ru> you write: > I successfully checked out and compiled Zsh from CVS. Congratulations! > > Offtopic: anybody knows, how to find out, what branch was checked out? > And the date? I mean, now, when reporting problems, we need some way to > refer to "CVS branch xxx checked out/updated at yyy" status -v will tell you if there is a sticky tag - including sticky branch tag - or sticky date for a particular file. It's pretty much up to you not to do anything foolish like check out different files from different branches. For the "checked out/updated at yyy" problem, I think the best solution is for most people to use labeled versions, which shouldn't be too onerous as long as folks are smart about creating new (and cleaning up old and useless) labels. -- David M. Meyer dmeyer0@bellatlantic.net