Fwd: FW: how can I keep some user from pushing outside of his branch

[Dave S]

Whoops, forgot to send to list

-d



---------- Forwarded message ----------
From: Dave S <snidely.too at gmail.com>
Date: Mon, Dec 7, 2015 at 12:43 PM
Subject: Re: FW: how can I keep some user from pushing outside of his branch
To: FLORENT Philippe <Philippe.FLORENT at edenred.com>


On Thu, Dec 3, 2015 at 4:20 AM, FLORENT Philippe
<Philippe.FLORENT at edenred.com> wrote:
> Strange nobody talket to me about phases

I'm not sure how they apply, although I'm not a phase guru.

>
>         The draft phase holds changesets that are not yet considered a part of the repository's permanent history. You can safely rewrite them. New commits are in the draft phase by default.
>
>         The secret phase holds changesets that you do not want to exchange with other repositories. Secret changesets are hidden from remote peers and will not be included in push operations. Manual operations or extensions may move a changeset into the secret phase.
>
> They seem to address this problem


I thought the crux of the problem was that your other user was doing a
pull/update and ending up on a tip that wasn't the branch he was
supposed to be working on.  It's unclear to me how the secret phase
would address this, other than making the default branch secret, and
that will probably introduce problems elsewhere in your flow.

I thought from previous messages that the way out of your mess was to
fix where the pull/update ended up.

/dps


>
> -----Original Message-----
> From: Becker, Mischa J [mailto:mischa.becker at kroger.com]
> Sent: lundi 30 novembre 2015 23:04
> To: FLORENT Philippe; mercurial at selenic.com
> Subject: RE: how can I keep some user from pushing outside of his branch
>
>> From: FLORENT Philippe
>> Sent: Friday, November 27, 2015 6:12 AM
>> Subject: how can I keep some user from pushing outside of his branch
>>
>> Hello,
>>
>> My colleague keeps pushing to the default branch (cos tortoisehg is an
>> annoying piece of crap) and as mercurial does not allow to go back so
>> it's all a bloody mess everytime
>>
>> Is there a way (.hgrc??) to keep if from pushing to the default branch ?
>>
>> thanks
>
> If you don't want TortoiseHg to push all changes by default, go into settings, select Sync on left and set the Default Push to Branch or Revision.  This defaults the push to changes on the current branch or changes on the current branch up to the current revision.
>
> This won't prevent the push from ever happening but should reduce accidents.
>
> Mischa
>
> ________________________________
>
> This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain information that is confidential and protected by law from unauthorized disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
> _______________________________________________
> Mercurial mailing list
> Mercurial at selenic.com
> https://selenic.com/mailman/listinfo/mercurial



--
test signature -- please apply at front gate on Tuesdays only.


-- 
test signature -- please apply at front gate on Tuesdays only.