On Thu, Jan 25, 2018 at 2:08 AM, Duy Nguyen wrote:
> On Wed, Jan 24, 2018 at 8:09 PM, Patryk Obara wrote:
>> This extension selects which hashing algorithm from vtable should be
>> used for reading and writing objects in the object store. At the moment
>> supports only single value (sha-1).
>>
>
On 26/01/2018 15:41, Johannes Schindelin wrote:
On Thu, 25 Jan 2018, Duy Nguyen wrote:
This config is so sensitive I wonder if we should forbid changing it
via git-config. You can't simply change this and expect anything to
work anyway.
I don't think it makes sense to forbid `git config` fro
Hi Duy,
On Thu, 25 Jan 2018, Duy Nguyen wrote:
> On Wed, Jan 24, 2018 at 8:09 PM, Patryk Obara wrote:
> > This extension selects which hashing algorithm from vtable should be
> > used for reading and writing objects in the object store. At the moment
> > supports only single value (sha-1).
> >
On Wed, Jan 24, 2018 at 8:09 PM, Patryk Obara wrote:
> This extension selects which hashing algorithm from vtable should be
> used for reading and writing objects in the object store. At the moment
> supports only single value (sha-1).
>
> In case value of objectFormat is an unknown hashing algor
Argh! Forgot to sign-off the commit…
--
| ← Ceci n'est pas une pipe
Patryk Obara
This extension selects which hashing algorithm from vtable should be
used for reading and writing objects in the object store. At the moment
supports only single value (sha-1).
In case value of objectFormat is an unknown hashing algorithm, Git
command will fail with following message:
fatal: u
6 matches
Mail list logo
