Making "hg push -r foo" changes phases

Pierre-Yves David pierre-yves.david at logilab.fr
Thu Jun 13 09:43:45 CDT 2013


On Thu, Jun 13, 2013 at 10:34:27AM -0400, Jordi Gutiérrez Hermoso wrote:
> Would it make sense that when doing "hg push -r foo" that foo become a
> draft or public phase if it was originally secret?
> 
> I find it odd that hg push -r foo won't push foo, even if I just
> explicitly requested it, just because foo is secret.

Foo may be a lot of things, a branch name, a bookmark, a revset or an explicite hash.

Making the distinction between those case is non trivial and maybe a bad idea.

I'm not sure to be able to define a proper definition for "explicitly requested".

Is this special case special enough?

-- 
Pierre-Yves David

http://www.logilab.fr/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20130613/83134feb/attachment.pgp>


More information about the Mercurial-devel mailing list