Re: Configuring a Checked out Zinf

"Kristian G. Kvilekval" <[email protected]>
Newsgroups gmane.comp.audio.zinf.devel
Message-ID <1060291801.6505.2.camel@merrimack>
Careful.  "release-2-2-4"  '.' is not allowed in a tag.

Another way to see what tags are available is
(pick any file i.e. README)
cvs log README
 
RCS file: /cvsroot/zinf/zinf/README,v
Working file: README
head: 1.2
branch:
locks: strict
access list:
symbolic names:
        release-2-2-4: 1.2
        lazydb: 1.2.0.2
        start_2-3-0: 1.2
        release-2-2-3: 1.2
        rpms-2-2-0: 1.1.0.2
        release-2-2-0: 1.1
        start: 1.1.1.1
        zinf: 1.1.1
keyword substitution: kv
total revisions: 3;     selected revisions: 3
description:


On Thu, 2003-08-07 at 14:21, Steve Holmes wrote:
> On Thu, Aug 07, 2003 at 10:42:21AM -0700, Kristian Kvilekval wrote:
> > Get a copy of 2.2.4.  This will have 
> > a valid configure script in it.
> > 
> > from your updated CVS dir
> > cvs diff -r release-2-2-4 > current-cvs.patch
> I tried that but it did not work! it said that "release-2.2.4" didn't
> exist.  BTW, I notice a lot of end-of-file errors from the server; it
> refers to messages above but there is never messages available.  I
> tried listing tags by 'cvs history -report -T' and I keep getting "no
> tags selected."  So I can't verify what the actual tag names are so I
> could do the diff command.  I gues another way would be to use a local
> diff command here and just use the cvs version of zinf minus the CVS
> directories?
-- 
email:[email protected] office:(805)893-4276 http://www.cs.ucsb.edu/~kris



-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.