From: Eric Sunshine <sunshine@sunshineco.com>
Date: Mon, 09 Dec 2019 22:50:17 GMT
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.
Message-ID: <CAPig+cR2=LZtsMtAR-0b5mvL6B161eGyM5th6CM3TQxLYmifxg@mail.gmail.com>
In-Reply-To: <xmqq1rtdt9rc.fsf@gitster-ct.c.googlers.com>

On Mon, Dec 9, 2019 at 5:27 PM Junio C Hamano <gitster@pobox.com> wrote:
> >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 an open issue[1] regarding that.

[1]: https://github.com/gitgitgadget/gitgitgadget/issues/120