[PATCH] lfs: add an experimental config to masquerade as git for the blob transfer

Matt Harbison mharbison72 at gmail.com
Thu Dec 14 23:37:30 EST 2017


On Thu, 14 Dec 2017 19:51:37 -0500, Sean Farley <sean at farley.io> wrote:

>
> Augie Fackler <raf at durin42.com> writes:
>
>>> On Dec 13, 2017, at 6:20 PM, Matt Harbison <mharbison72 at gmail.com>  
>>> wrote:
>>>
>>>
>>> On Dec 13, 2017, at 9:48 AM, Augie Fackler <raf at durin42.com  
>>> <mailto:raf at durin42.com>> wrote:
>>>
>>>>
>>>> I don't either. Do whichever of the versions that mentions hg that  
>>>> makes you happier?
>>>>
>>>> (I think we should default to not advertising as git, so that people  
>>>> can file bugs? Or is that a bad UX?)
>>>
>>> That’s what I initially thought, and how I coded it. I do think that’s  
>>> potentially a bad UX though. After seeing the example in the RFC, I  
>>> wonder if we should just put in both identifiers and be done with it.
>>
>> Works for me.
>>
>> (For optional bonus points, leave the config option so we can force a  
>> sane user-agent and at least eager hg devs can smoke out bad LFS  
>> servers? I don’t feel strongly though.)
>
> I can't speak for other LFS hosts but I can at least make sure the
> Bitbucket side works with either header.

OK, good, thanks.

Is there anything else that would be useful to coordinate with Bitbucket?   
(I can't think of anything, other than I'd like to make the lfs.url  
sidecar config optional, and be able to send it to the push destination by  
default.  That seems to be how git works, IIUC.)


More information about the Mercurial-devel mailing list