summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorsnappy.mirrorbot@gmail.com <snappy.mirrorbot@gmail.com@03e5f5b5-db94-4691-08a0-1a8bf15f6143>2011-06-04 10:19:05 +0000
committersnappy.mirrorbot@gmail.com <snappy.mirrorbot@gmail.com@03e5f5b5-db94-4691-08a0-1a8bf15f6143>2011-06-04 10:19:05 +0000
commit28be69c36a9a40e396c72ea587b2c68d523a3844 (patch)
treef02849e303d08b6cc40313d5faed905eaf097695
parent23805f9d5fbcdf4b0d4b94b530f3d81124d8ba63 (diff)
downloadsnappy-28be69c36a9a40e396c72ea587b2c68d523a3844.tar.gz
Correct an inaccuracy in the Snappy format description.
(I stumbled into this when changing the way we decompress literals.) R=csilvers Revision created by MOE tool push_codebase. git-svn-id: http://snappy.googlecode.com/svn/trunk@43 03e5f5b5-db94-4691-08a0-1a8bf15f6143
-rw-r--r--format_description.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/format_description.txt b/format_description.txt
index 943bfc2..31e717c 100644
--- a/format_description.txt
+++ b/format_description.txt
@@ -52,7 +52,7 @@ of the literal:
- For literals up to and including 60 bytes in length, the upper
six bits of the tag byte contain (len-1). The literal follows
immediately thereafter in the bytestream.
- - For longer literals, the length is stored after the tag byte,
+ - For longer literals, the (len-1) value is stored after the tag byte,
little-endian. The upper six bits of the tag byte describe how
many bytes are used for the length; 60, 61, 62 or 63 for
1-4 bytes, respectively. The literal itself follows after the