mercurial/help/internals/wireprotocolv2.txt
changeset 40391 abbd077965c0
parent 40329 ed55a0077490
child 40924 08cfa77d7288
--- a/mercurial/help/internals/wireprotocolv2.txt	Fri Oct 19 14:59:03 2018 +0200
+++ b/mercurial/help/internals/wireprotocolv2.txt	Fri Oct 19 15:38:25 2018 +0200
@@ -258,6 +258,9 @@
    (set of bytestring) Which data associated with a file to fetch.
    The following values are recognized:
 
+   linknode
+      The changeset node introducing this revision.
+
    parents
       Parent nodes for the revision.
 
@@ -355,6 +358,9 @@
    (set of bytestring) Which data associated with a file to fetch.
    The following values are recognized:
 
+   linknode
+      The changeset node introducing this revision.
+
    parents
       Parent nodes for the revision.
 
@@ -422,6 +428,9 @@
 
 TODO we'll probably want a more complicated mechanism for the client to
 specify which ancestor revisions are known.
+TODO we may want to make linknodes an array so multiple changesets can be
+marked as introducing a file revision, since this can occur with e.g. hidden
+changesets.
 
 heads
 -----