push with more head on local repo

[Bill Barry]

As a new named branch, it shouldn't have given you a warning at all 
(that is a bug).

Martin Marques wrote:
> Craig Neth escribió:
>   
>> Is there a good reason for this message to suggest the -f option?
>>
>> Every time our project adds new members we generally have some misuse of 
>> the -f on push - what they really wanted  to do was to pull/fetch first, 
>> instead of forcing their push with -f.
>>     
>
> As I am the OP: I want the new branch on the main repo.
>
> Actually, it's a small project where I work around documentation in TEX 
> and I build named branches for the courses I give. Right now I'm going 
> to give a new one, so I made a named branch for it, where I make changes 
> that are only related with that course.
> _______________________________________________
> 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/20080523/8d99ca24/attachment.htm