From d0ee043bc50c62c5b5ff3da044f0b5567257407d Mon Sep 17 00:00:00 2001 From: "snappy.mirrorbot@gmail.com" Date: Tue, 17 May 2011 08:48:25 +0000 Subject: [PATCH] Fix the numbering of the headlines in the Snappy format description. R=csilvers DELTA=4 (0 added, 0 deleted, 4 changed) Revision created by MOE tool push_codebase. MOE_MIGRATION=1906 git-svn-id: https://snappy.googlecode.com/svn/trunk@37 03e5f5b5-db94-4691-08a0-1a8bf15f6143 --- format_description.txt | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/format_description.txt b/format_description.txt index f5b990e..943bfc2 100644 --- a/format_description.txt +++ b/format_description.txt @@ -1,5 +1,5 @@ Snappy compressed format description -Last revised: 2011-05-13 +Last revised: 2011-05-16 This is not a formal specification, but should suffice to explain most @@ -86,7 +86,7 @@ the amount of bytes to be copied (length), and how far back the data to be copied is (offset). -2.2. Copy with 1-byte offset (01) +2.2.1. Copy with 1-byte offset (01) These elements can encode lengths between [4..11] bytes and offsets between [0..2047] bytes. (len-4) occupies three bits and is stored @@ -95,7 +95,7 @@ upper three are stored in the upper three bits ([5..7]) of the tag byte, and the lower eight are stored in a byte following the tag byte. -2.3. Copy with 2-byte offset (10) +2.2.2. Copy with 2-byte offset (10) These elements can encode lengths between [1..64] and offsets from [0..65535]. (len-1) occupies six bits and is stored in the upper @@ -103,7 +103,7 @@ six bits ([2..7]) of the tag byte. The offset is stored as a little-endian 16-bit integer in the two bytes following the tag byte. -2.4. Copy with 4-byte offsets (11) +2.2.3. Copy with 4-byte offsets (11) These are like the copies with 2-byte offsets (see previous subsection), except that the offset is stored as a 32-bit integer instead of a