[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Exporting file versions
From: |
Larry Jones |
Subject: |
Re: Exporting file versions |
Date: |
Tue, 15 Oct 2002 17:59:24 -0400 (EDT) |
Jason Yeung writes:
>
> MIME-Version: 1.0
> Content-Type: multipart/alternative;
Please do not post MIME and/or HTML encrypted messages to the list.
Plain text only, PLEASE!
> I'm trying to use the export command to export files of a given
> revision, but am unsuccessful. The command and options I ran is "cvs
> export -r 1.2 -d testing testing123" and the error I get is "tag `1.2'
> must be a symbolic tag". If I create tags to represent the revisions and
> run and "cvs export -r ver12 -d testing testing123" (ver12 represents
> all files in revision 1.2), it'll export OK.
>
> Because my project has a lot of files, creating tags for each version of
> a file would be very tedious. I was wondering if there's a way to export
> files without creating tags? If you need tags to export, what would be
> the easiest way to create the tags without going through every file and
> create tags individually?
You're confusing the revision numbers of the individual files with the
revision number of your module. The revision number of a file changes
every time you commit a change to it, so you'll almost never have all
the files with the same revision number. What you should do is ignore
the file revision numbers and apply a tag (like ver12) when you make a
"release" of the module as a whole and then use that tag whenever you
want to refer to that release in the future.
-Larry Jones
Some people just don't have inquisitive minds. -- Calvin