Argh. New problem with branches

[Jesse Keating]

On Wed, 12 Sep 2007 07:21:00 -0400
Jesse Keating <jkeating at redhat.com> wrote:

> Just can't seem to get them right.
> 
> Given a repo that has multiple branches, "default" and "coolbranch".
> Clone the repo, notice that current branch is "default".  Do a pull,
> do an update just to make sure you're all updated.  Make some change
> to the working copy, commit it, and push.
> 
> pushing to /home/jkeating/test/head
> searching for changes
> abort: push creates new remote branches!
> (did you forget to merge? use push -f to force)
> 
> Now why would that be?  There are no other changes on the 'default'
> branch, so this change shouldn't create a new head, it should just
> commit to the default branch.

Ping, is this a bug I'm seeing or am I doing something wrong here?  I"d
really like to continue using mercurial, but if I can't work out this
branching stuff I have to move on :/

-- 
Jesse Keating
Fedora -- All my bits are free, are yours?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://selenic.com/pipermail/mercurial/attachments/20070913/2df82986/attachment.pgp