push with more head on local repo

[Bill Barry]

Is there any way to get it to not warn when it creates a new head that 
is a named branch? I still want it to warn if it creates a new head on 
the same named branch, but when creating a new named branch I would 
assume creating a new head is deliberate.

Jamie Webb wrote:
> On 2008-05-20 17:39:32 Martin Marques wrote:
>   
>> If I push changesets from my local repo to my main repository, and I 
>> have an extra head, I get an abort like this:
>>
>> $ hg push
>> pushing to /home/martin/hg/cursos
>> searching for changes
>> abort: push creates new remote branches!
>> (did you forget to merge? use push -f to force)
>>
>> I know what it means, but I would like to know what would happen if I 
>> force the push with -f. Will it just add the new head? That is
>> exactly waht I want (the new head is actually a named branch).
>>     
>
> Yes, that's right.
>
> /J
> _______________________________________________
> Mercurial mailing list
> Mercurial at selenic.com
> http://selenic.com/mailman/listinfo/mercurial
>
>   

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://selenic.com/pipermail/mercurial/attachments/20080521/f5228e7b/attachment.htm