Re: Change Default Branch

[Libin Varghese]

Hi Michael,

I have read some content on the Web regarding this... below are few extracts

<extract url="http://gforge.org/themes/gforgegroup/viewvc/help_rootview.html";>
In CVS Repositories, ViewCVS adds artificial tags HEAD and MAIN to tag
listings and accepts them in place of revision numbers and real tag
names in all URLs. MAIN acts like a branch tag pointing at the default
branch, while HEAD acts like a revision tag pointing to the latest
revision on the default branch. The default branch is usually just the
trunk, but may be set to other branches inside individual repository
files. CVS will always check out revisions from a file's default
branch when no other branch is specified on the command line.
</extract>

<extract url="http://www.devguy.com/fp/cfgmgmt/cvs/";>
   4. Run the following command
      cvs admin -b
   5. Update your sandbox
      cvs update -A newmodule

This is a fast way to create a module and ensures that you (and
everyone elsewho does a subsequent checkout) will be poised to work on
the trunk.
</extract>

As I mentioned earlier, I did try the admin -b.

On Tue, Mar 4, 2008 at 1:07 AM, Michael Haggerty <address@hidden> wrote:
>
> Libin Varghese wrote:
>  > I have created branch (NEW_BRANCH) from the Trunck/MAIN Branch for a
>  > Module. Then I have updated 3 of N files in this NEW_BRANCH. Now I
>  > want to make this NEW_BRANCH as the default branch (ie. if I don't
>  > give a -r option in my checkout NEW_BRANCH has to be checked out). Can
>  > someone please suggest as to how I can achieve this?
>  >
>  > I tried with "cvs admin -bNEW_BRANCH" , but when I checkout without -r
>  > option only those 3 file which was updated are checked out.
>
>  As far as I understand, the "default branch" feature is not meant to be
>  a general way of choosing which branch should be checked out by default.
>   I believe it is meant for a very particular and purpose related to
>  vendor branches.  And using "cvs admin -b" even in the case of vendor
>  branches is also a questionable practice.
>
>  Consider merging the changes from NEW_BRANCH back to the main line of
>  development instead of trying to change the default branch.
>
>  Michael
>