Submitter | Matt Harbison |
---|---|
Date | Oct. 18, 2018, 2:09 a.m. |
Message ID | <197a387c4ed9a510a5d9.1539828540@Envy> |
Download | mbox | patch |
Permalink | /patch/36113/ |
State | Accepted |
Headers | show |
Comments
On Wed, 17 Oct 2018 22:09:00 -0400, Matt Harbison wrote: > # HG changeset patch > # User Matt Harbison <matt_harbison@yahoo.com> > # Date 1539824743 14400 > # Wed Oct 17 21:05:43 2018 -0400 > # Node ID 197a387c4ed9a510a5d92e68e7be7752b327cb99 > # Parent d916ed3ca951a3bfd37bf29f54dc70f82787512a > help: document the server capabilities added by the LFS extension Queued, thanks.
Patch
diff --git a/mercurial/help/internals/wireprotocol.txt b/mercurial/help/internals/wireprotocol.txt --- a/mercurial/help/internals/wireprotocol.txt +++ b/mercurial/help/internals/wireprotocol.txt @@ -702,6 +702,25 @@ Whether the server supports the ``known` This capability/command was introduced in Mercurial 1.9 (released July 2011). +lfs +--- + +Indicates that the LFS extension is enabled on the server. It makes no claims +about the repository actually having LFS blobs committed to it. + +This capability was introduced by the LFS extension in Mercurial 4.5 (released +Feb 2018). + +lfs-serve +--------- + +Indicates that the LFS extension is enabled on the server, and LFS blobs are +committed to the remote repository. (Specifically, it indicates that the 'lfs' +requirement is present in the remote repository.) + +This capability was introduced by the LFS extension in Mercurial 4.8 (released +Nov 2018). + lookup ------