Valid values for the phases.new-commit settings\

Pierre-Yves David pierre-yves.david at logilab.fr
Mon Feb 6 10:03:38 UTC 2012


On Sun, Feb 05, 2012 at 08:50:57PM +0100, Angel Ezquerra wrote:
> On Feb 5, 2012 7:31 PM, "Matt Mackall" <mpm at selenic.com> wrote:
> >
> > On Sun, 2012-02-05 at 13:22 +0100, Angel Ezquerra Moreu wrote:
> > > Hi,
> > >
> > > I want to add support for setting the phases.new-commit setting
> > > through the TortoiseHg settings dialog. What are the valid values for
> > > for that setting?
> >
> > Public, draft, and secret. But I recommend you not add support for this
> > setting until people demonstrate a need for it.
> >
> > --
> > Mathematics is the supreme nostalgia of our time.
> >
> >
> 
> That was my guess, but I wanted to make sure.
> 
> The main reason I thought of adding support for that setting is that it was
> specifically mentioned by Pierre-Yves on his blog.
> 
> I recon that you think this its an advanced feature? I imagine that it
> could come in handy to be able to make your commits secret while you give
> temporary pull access to someone else to one of your repos, for example.
> 
> Angel

This options was exposed in the "how to control phases" part of the series of
blog. It's maintly here to show that people may have a lot of control over
phases if they need too. This does not meant that their is actual people who
want to use this yet.

Anyway, we could update hgrc documentation to mention valid values for this option.

-- 
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://lists.mercurial-scm.org/pipermail/mercurial-devel/attachments/20120206/2166c7a9/attachment.asc>


More information about the Mercurial-devel mailing list