This theory does not hold if more than one tag is on the latest revision of a
file. It also does not indicate the latest tag across all branches. It does
not appear that the date of a tag is stored in the ,v file, so it is probably
not possible to always determine the latest tag.
Rex.
Stephen Rasku <[EMAIL PROTECTED]> on 07/27/2000 09:14:07 AM
Please respond to Stephen Rasku <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
cc: (bcc: Rex Jolliff/YM/RWDOE)
Subject: Re: Sorting tags
>From: "Reinstein, Shlomo" <[EMAIL PROTECTED]>
>To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
>Subject: Sorting tags
>Date: Thu, 27 Jul 2000 06:14:11 -0700
>X-Mailing-List: <[EMAIL PROTECTED]> archive/latest/19057
>
>Hi,
>
>Is there a way of sorting tags according to the revisions that
they tag?
>Specifically I would like to find the latest tag that was put
on a given
>branch. (Suppose that all files in a CVS project are always
tagged
>together, so in general I could take the output of "cvs log"
for any single
>file to see all tags.)
>
The latest tag should be the one with the biggest revision
number. So, for the following output:
symbolic names:
arbitrary-tag: 1.1.4.1
before-purify-fixes: 1.1.4.2
bug-351: 1.1.0.4
ok-to-checkin: 1.1.1.2
rel-2_3: 1.1.0.2
recover-2_4: 1.1.1.2
recover-2_3: 1.1.1.1
stephen: 1.1.1
The latest tag on the bug-351 branch is before-purify-fixes.
The bug-351 branch is 1.1.0.4 so all files on this branch will
start with 1.1.4. Therefore, the tags arbitrary-tag and
before-purify-fixes are both on this branch. Since 1.1.4.2 is
greater than 1.1.4.1 it is the later tag.
--
Stephen Rasku E-mail: [EMAIL PROTECTED]
Senior Software Engineer Web: http://www.tgivan.com/
TGI Technologies http://www.pop-star.net/
