Making it easy to really create private local branching

[Martin Geisler]

dukeofgaming <dukeofgaming at gmail.com> writes:

> On Sun, Jan 6, 2013 at 6:49 PM, Pierre-Yves David <
> pierre-yves.david at ens-lyon.org> wrote:
>
>>
>> On 7 janv. 2013, at 01:17, dukeofgaming wrote:
>>
>> > Then there are Mercurial Phases to do this, but it is slightly
>> > cumbersome IMHO, enough to somewhat discourage their use:
>> >
>> > # hg branch my_branch
>> > # hg commit -m "Opening branch"
>> > # hg id -n
>> > 123
>> > # hg phase --secret --force 123
>>
>> The `hg id` is unneeded here:
>>
>
> Not unless you use the GUI or somehow are able to guess the next revision
> number. So `hg id` is necessary for usability reasons IMHO.

I think Pierre-Yves wanted to say that you can use '.' as a reference to
the working copy parent revision. So this command will make the newly
committed changeset secret:

  $ hg phase --secret --force .

-- 
Martin Geisler
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20130107/769ac499/attachment.pgp>