Re: Tag updations

On 2007-06-08 08:02:55, Bo Berglund wrote:

> If you tag your checked out files with TagB then to get the file set to
> become locked to TagB all you have to do is to do a cvs update and give
> the tag name as the -r parameter. Or enter it into the WinCvs update
> dialogue...

> If you want to get your local files to TagA instead then you do the same
> type of update but give the TagA name instead. 

If you regularly want to check files in both tags, you can also have a
checked out copy of each. Just run one checkout to one location with TagA,
and another checkout to another location with TagB. 

I have often a sandbox structure like this:

+ Project_1
    |
    + Firmware        << HEAD (development)
        |
        ...
    + Firmware.TagA   << specific release
        |
        ...
    + Firmware.TagA   << another specific release
        |
        ...

Firmware, Firmware.TagA and Firmware.TagB are copies of the same files from
the repository, just that Firmware is the tip of HEAD and the other two
directories are checkouts of the two tags. With this I have all three
versions of the code always present and I don't have to commit/update just
for working with the code in one of the tags.

Gerhard



 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/cvsgui/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/cvsgui/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:[email protected] 
    mailto:[email protected]

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/