title: Named previously unnamed branch
body: <p>It seems naming a previously unnamed branch doesn't really work out. It creates a nasty multiple heads problem that I can't find a solution for.</p>
  
  <p>Here is the workflow...</p>
  
  <p>UserA starts working on feature that they expect to be small, so they just start working(off the <code>default</code> branch). The change turns out to be a large project and will need multiple contributors. So UserA issues... <code>hg branch "Feature1"</code> and continues working, committing locally s needed.</p>
  
  <p>UserA then pulls down the changes from the central repo so he can push.  </p>
  
  <p>At this point, why does <code>hg heads</code> return <strong>3</strong> heads? It shows 2 for <code>default</code> and 1 for <code>Feature1</code>. The first head for <code>default</code> is the latest change by another user on the branch(irrelevant).  The second <code>default</code> head is the commit prior to the <code>hg branch "Feature1"</code> commit.</p>
  
  <p>The  <strong>central repository has rules enforced so that only 1 head per branch is allowed</strong>, so forcing a push isn't an option.  The repo doesn't want multiple heads on the <code>default</code> branch.</p>
  
  <p>UserA should be able to push these changes so that other users can see the <code>Feature1</code> branch and help out. I can't seem to find a way to "correct" this. I don't think I can re-write the branch of the initial commits for the feature, before it was a named branch. </p>
  
  <p>I know the initial changes before the named branch are technically on the default branch, but does that mean they will be heads until that <code>Feature1</code> branch is merged?</p>