[PATCH 3 of 4] revlog: remove some revlogNG terminology
Gregory Szorc
gregory.szorc at gmail.com
Fri May 19 23:58:59 EDT 2017
# HG changeset patch
# User Gregory Szorc <gregory.szorc at gmail.com>
# Date 1495250071 25200
# Fri May 19 20:14:31 2017 -0700
# Node ID 653a47e013ae71470ae943e5c9a84e92eae0676e
# Parent 26a43d84eb714ee6bba04f21c0264ded9215a3bd
revlog: remove some revlogNG terminology
RevlogNG is not such a good name when it is no longer the
newest revlog version. Since we'll soon have revlog version 2,
let's remove some references to it.
diff --git a/mercurial/help/internals/revlogs.txt b/mercurial/help/internals/revlogs.txt
--- a/mercurial/help/internals/revlogs.txt
+++ b/mercurial/help/internals/revlogs.txt
@@ -60,23 +60,23 @@ 2-15
The following header values are common:
00 00 00 01
- RevlogNG
+ v1
00 01 00 01
- RevlogNG + inline
+ v1 + inline
00 02 00 01
- RevlogNG + generaldelta
+ v1 + generaldelta
00 03 00 01
- RevlogNG + inline + generaldelta
+ v1 + inline + generaldelta
Following the 32-bit header is the remainder of the first index entry.
Following that are remaining *index* data. Inlined revision data is
possibly located between index entries. More on this layout is described
below.
-RevlogNG Format
-===============
+Version 1 Format
+================
-RevlogNG (version 1) begins with an index describing the revisions in
+Version 1 (RevlogNG) begins with an index describing the revisions in
the revlog. If the ``inline`` flag is set, revision data is stored inline,
or between index entries (as opposed to in a separate container).
diff --git a/mercurial/revlog.py b/mercurial/revlog.py
--- a/mercurial/revlog.py
+++ b/mercurial/revlog.py
@@ -187,7 +187,7 @@ class revlogoldio(object):
def packentry(self, entry, node, version, rev):
if gettype(entry[0]):
- raise RevlogError(_("index entry flags need RevlogNG"))
+ raise RevlogError(_('index entry flags need revlog version 1'))
e2 = (getoffset(entry[0]), entry[1], entry[3], entry[4],
node(entry[5]), node(entry[6]), entry[7])
return _pack(indexformatv0, *e2)
More information about the Mercurial-devel
mailing list