We do both for onnv-clone.
Although technically it is {REPO}/.hg/store that Mercurial looks
at for creating new files in the store (it uses that as a kind of umask).
But its best to make sure everything in and including .hg can't be
written to by group or other. But with default umask of 022 that
Dan Mick wrote:
> Tushar Desai wrote:
>> Dan Mick wrote:
>>> I want to make a repo be pull-from-only (readonly, in essence). Is
>>> the best/most-complete way to make .hg/ nonwritable?
>>>
>> The below is what we did to accomplish what you want to get done
>>
>> add the below in .hgrc
>
> But
Tushar Desai wrote:
> Dan Mick wrote:
>> I want to make a repo be pull-from-only (readonly, in essence). Is
>> the best/most-complete way to make .hg/ nonwritable?
>>
> The below is what we did to accomplish what you want to get done
>
> add the below in .hgrc
But doesn't this require the us
Dan Mick wrote:
> I want to make a repo be pull-from-only (readonly, in essence). Is the
> best/most-complete way to make .hg/ nonwritable?
>
The below is what we did to accomplish what you want to get done
add the below in .hgrc
[hooks]
pretxnchangegroup.deny.lock = path to the lock script
I want to make a repo be pull-from-only (readonly, in essence). Is the
best/most-complete way to make .hg/ nonwritable?
