publish =False to True, no change

[Uwe Brauer]

Hello Paul,


   > On 10/10/18 1:11 PM, Uwe Brauer wrote:

   > Hello Uwe,

   > This setting is telling Mercurial that your repository is not
   > publishing. That is, when changesets are exchanged with it, whether
   > they become public or remain draft.
   > From the behavior you describe, I guess that the bitbucket repository is
   > set as non-publishing (Settings, Repository details, Phases: [x] This is
   > a non-publishing repository).

I will check that, thanks for pointing out. Yes you are right. 

That repo is indeed private, that is I collaborate just with one other
author and we both push and pull there. I want to leave it this way, so,
if I understand you correctly, I better got back to my original setting.

Or is it just that the setting has no effect at all, if the repo is that
this way?

   > If you want to have this publishing behavior for all your pushes, then
   > you can uncheck this checkbox.
   > However, you will probably prefer to choose when you publish or not. The
   > command to publish a changeset is:

   >     hg push --publish -r changeset

Just to be sure that there is no misunderstanding, I want my bitbucket
repo to be private not public.  So 

    1. What will hg push --publish -r changeset
       do for such a repo.

    2. Is it better to have 
[phases]
publish = False
   
     for such a repo?

Uwe 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5025 bytes
Desc: not available
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20181010/17d0314b/attachment.p7s>