Re: [PATCH v2 1/1] "git lfs" allows users to specify the custom storage location by configuration variable lfs.storage, but when "git p4" interacts with GitLFS pointers, it always used the hardcoded default that is the .git/lfs/ directory, without paying attention to the configuration.

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Dec 10, 2019, 12:19 UTC
Message-ID: <nycvar.QRO.7.76.6.1912101317340.31080@tvgsbejvaqbjf.bet>
In-Reply-To: <xmqq1rtdt9rc.fsf@gitster-ct.c.googlers.com>

Hi Junio,

On Mon, 9 Dec 2019, Junio C Hamano wrote:

Show 8 quoted lines

> "panzercheg via GitGitGadget" <gitgitgadget@gmail.com> writes:
>
> >Subject: Re: [PATCH v2 1/1] "git lfs" allows users to specify the custom storage location by configuration variable lfs.storage, but when "git p4" interacts with GitLFS pointers, it always used the hardcoded default that is the .git/lfs/ directory, without paying attention to the configuration.
>
> Oops, what happened here?
>
> I wonder/I wish if GGG can be a bit more helpful when seeing a
> commit that looks "strange".

There is already a ticket about that: https://github.com/gitgitgadget/gitgitgadget/issues/120

All it requires is a contributor with a little time :-)

Show 9 quoted lines

> > From: panzercheg <panzercheg@gmail.com>
> >
> > Use the value configured in lfs.storage, if exists, as all the
> > "git" operations do, for consistency.
> >
> > Signed-off-by: r.burenkov <panzercheg@gmail.com>
>
> Please make sure that the name/email as the author matches whom you
> sign-off the patch as.

This, too, should be addressed as part of above-mentioned ticket.

Ciao, Dscho