Terminology: what to call the trunk

[Bill Barry]

Greg Ward wrote:
> Hmmm.  I'll have to play with this, but I'm thinking of this:
>
>   hg init
>   hg branch trunk
>   # start hacking and committing...
>
> Then *poof* the branch that I chose to call "trunk" is the mainline of
> development.  Is this likely to cause problems?  I.e. are there
> commands/extensions/tools out there that expect branch '' (aka
> 'default') to exist?
>   
This is exactly what we did for our main repo and we haven't seen any 
problems yet (though the docs do say to avoid doing this I think mostly 
because it isn't an expected convention). One quick note is that when 
you do this hg clone will not properly update to the correct revision 
right away I think. You will have to do hg clone ... and then "hg update 
-C trunk"

generally what we do to clone a new copy is:

hg init
hg pull ...
hg up -C trunk

instead of hg clone. Then we go in and set up the default pull/push 
location in the hgrc file (our local machines all have names/passwords 
defaulted to them; probably not the most secure situation, but we figure 
that if an attacker has gotten this far then security is already a lost 
cause).