Xavier de Gaye wrote:
> On Sun, May 23, 2010 at 12:38 PM, Bram Moolenaar wrote:
> >
> > ...
> > When 7.3 is released it will become the default branch. =A0How this is
> > done I don't know. ...
> >
>
>
> The 'vim73' branch can be given the name of the 'default' branch with
> the 'hg branch --force default' command after the 'default' branch is
> named 'vim72' with the 'hg branch vim72' command (both followed by
> commit).
>
> A simple test made on a fake repo with 'default' and 'vim73' branches
> (same as in the current vim repo) shows this result after that is done:
>
> $ hg branches
> default 5:ce5266650699
> vim72 4:d5bb6abbab9a
> vim73 3:90078dbe59dd (inactive)
>
> Changeset '3:90078dbe59dd' is the tip of the vim73 branch before it is
> renamed to 'default'.
Now that I'm ready to make vim73 the default branch, it occurs to me
that when I do this, doing "hg update vim73" will stop working.
What I would like to do is keep the "vim73" label on the branch, but
make it the default one.
So currently:
hg clone ... gives you the default branch, Vim 7.2.1234
hg update vim73 switches to Vim 7.3
What I would like to get:
hg clone ... gives you the default branch, Vim 7.3.001
hg update vim73 stays on the default branch
hg update vim72 switches to Vim 7.2.1234
Is that possible? Or does making vim73 the default branch always have
the result that switching to the vim73 branch stops working?
An acceptable alternative would be that the default branch has the
latest version, including patches, while "vim73" is plain 7.3, no patches.
--
hundred-and-one symptoms of being an internet addict:
80. At parties, you introduce your spouse as your "service provider."
/// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ download, build and distribute -- http://www.A-A-P.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
