On Tue, Jul 29, 2014 at 12:46 PM, Stephan Beal
wrote:
> On Tue, Jul 29, 2014 at 6:25 PM, Ron W wrote:
>
>> the push (assuming autosunc isn't pull-only AND the local repo is not
>> no-push).
>>
>
> i didn't know about that option (it's called dont-push, though)
>
>dont-pushPrevent thi
On Tue, Jul 29, 2014 at 6:25 PM, Ron W wrote:
> the push (assuming autosunc isn't pull-only AND the local repo is not
> no-push).
>
i didn't know about that option (it's called dont-push, though)
dont-pushPrevent this repository from pushing from client to
server.
Thus said Ron W on Tue, 29 Jul 2014 12:25:08 -0400:
> Making autosync default to pull-only would not impact minimize
> unintentional forks.
Actually, it would. Consider this scenario.
Tizio clones and uses default autosync.
Caglio clones and enabled pull-only.
Tizio commits something.
C
On Mon, Jul 28, 2014 at 10:10 PM, Andy Bradford
wrote:
> Thus said Baruch Burstein on Sun, 27 Jul 2014 23:31:17 +0300:
> > Maybe this should be the default always, even if I have write
> > permission, in order to prevent accidental pushes?
>
> I believe changing the default for autosyn
On Tue, Jul 29, 2014 at 5:10 AM, Andy Bradford
wrote:
> > When cloning a repository, if I don't have write privileges, can
> > autosync by default be set to "pullonly" in the clone, to prevent
> > annoying "pull only - not authorized to push"?
>
> Are you suggesting that the clone dete
Thus said Baruch Burstein on Sun, 27 Jul 2014 23:31:17 +0300:
> When cloning a repository, if I don't have write privileges, can
> autosync by default be set to "pullonly" in the clone, to prevent
> annoying "pull only - not authorized to push"?
Are you suggesting that the clone detect
When cloning a repository, if I don't have write privileges, can autosync
by default be set to "pullonly" in the clone, to prevent annoying "pull
only - not authorized to push"? Maybe this should be the default always,
even if I have write permission, in order to prevent accidental pushes?
--
˙uʍ
7 matches
Mail list logo
