summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorJohn Wiegley <johnw@newartisans.com>2023-11-24 23:33:59 -0800
committerJohn Wiegley <johnw@newartisans.com>2024-08-05 08:35:56 -0700
commit67de3bce35de8158cd25750901a322cc02071c95 (patch)
tree984346a9cdd73dcd7c9dbc9175143e1f759a8263 /doc
parent6e9fda06df1754f58c347e44a4579d059dfd36f0 (diff)
downloadledger-67de3bce35de8158cd25750901a322cc02071c95.tar.gz
ledger-67de3bce35de8158cd25750901a322cc02071c95.tar.bz2
ledger-67de3bce35de8158cd25750901a322cc02071c95.zip
Make xact hashes independent of posting order
Also, support matching provided hashes against a prefixed of the generated hash.
Diffstat (limited to 'doc')
-rw-r--r--doc/ledger3.texi12
1 files changed, 9 insertions, 3 deletions
diff --git a/doc/ledger3.texi b/doc/ledger3.texi
index b4f3baab..ad41b985 100644
--- a/doc/ledger3.texi
+++ b/doc/ledger3.texi
@@ -6760,9 +6760,15 @@ Record the hash of each transaction in a @var{Hash} metadata value,
according to the hashing algorithm given by the @var{ALGO}
argument. Note that if a @var{Hash} metadata value is explicitly
provided and does not match what would have been generated, an error is
-reported. Hashes depend on previous entries, such that setting a single
-hash value is sufficient to guarantee the shape of the entire history
-leading up to that entry.
+reported. This provided value can also just be a prefix, at whatever
+length the user wishes, in which case only this amount of text is
+compared to the generated hash. Printing the entry with hashes enabled
+will display both this explicit metadata setting and the internally
+generated hash value.
+
+Hashes depend on previous entries, such that setting a single hash value
+is sufficient to guarantee the shape of the entire history leading up to
+that entry.
@item --head @var{INT}
@itemx --first @var{INT}