[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Vendor Tag & Release Tag

From: Kaz Kylheku
Subject: Re: Vendor Tag & Release Tag
Date: Sun, 09 Sep 2001 17:56:36 GMT
User-agent: slrn/ (Linux)

In article <address@hidden>, eric07 wrote:
>What are these used for.  Using WinCVS and when importing there is a

A release tag marks the vendor import on the vendor branch, which
is quite useful. It allows you to do things like view the differences
between one import and the next. It's critical for each import
to be tagged on the vendor branch.

The vendor tag is almost completely useless.  The reason it is useless
is that it does not really select the vendor you are importing from.
Unless you specify an alternate branch number  with the -b option,
the vendor import always goes to branch 1.1.1.  The vendor tag essentially
becomes a branch tag for branch 1.1.1 in every file. If you do two
successive imports, and use a different spellings for the vendor tag,
then you will simply have two tags specifying branch 1.1.1.

Vendor branches are always rooted at version 1.1 of every file. Unlike
normal branches, they have odd numbers: 1.1.1, 1.1.3, 1.1.5. This way
they won't conflict with branches that you may create off version 1.1 of
a file; these will be automaticlly assigned even numbers: 1.1.2, 1.1.4,
and so on.

If you want to keep track of changes from two different vendors, you
must manually select branch (for example) 1.1.3 for one of them
each time you do the import using the -b option.

I think the idea is that in the future, it will be sufficient to specify
the vendor tag alone, and it will intelligently create a new odd-numbered
branch, or select an existing one if the tag exists already.

Note that WinCVS UI doesn't have any provision for specifying the vendor
branch number; it has no interface to the -b option. (I fixed that in
a stream of WinCVS that I'm maintaining for the company I work for).

reply via email to

[Prev in Thread] Current Thread [Next in Thread]