Upstreaming Facebook extensions
mharbison72 at gmail.com
Mon Nov 13 22:49:56 EST 2017
On Mon, 13 Nov 2017 22:12:31 -0500, Jun Wu <quark at fb.com> wrote:
> Excerpts from Matt Harbison's message of 2017-11-13 21:50:29 -0500:
> For LFS, it has been used in a repo synced from p4 for about half a year.
> It's mostly good except for lack of features (ex. support the Git-LFS SSH
> authentication, support gc, etc.). It was actually written with some
> care of upstream-friendliness. For example, I put remotefilelog
> in remotefilelog instead of LFS intentionally.
> Help is definitely welcomed!
OK, good to know.
So is upstreaming lfs in a single patch and marking it experimental a
reasonable next step, or does this need to incubate in hg-experimental a
bit more? I didn't get it working outside of the tests (it said something
about not having a common changegroup version), but it looks like there's
some low hanging fruit like registering the config options, and tracking
down some warning in url.py about an "unquoted realm" or similar.
I know BC doesn't apply to experimental things, but realistically, I
assume things won't need to change other that maybe config stuff to add
features? I wouldn't mind using this sooner rather than later if the
files can always be retrieved.
More information about the Mercurial-devel