git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Martin Ågren" <martin.agren@gmail.com>
To: Ross Light <ross@zombiezen.com>
Cc: git@vger.kernel.org
Subject: [PATCH 0/2] pack-format.txt: document lengths at start of delta data
Date: Mon, 21 Dec 2020 08:54:57 +0100	[thread overview]
Message-ID: <cover.1608537234.git.martin.agren@gmail.com> (raw)
In-Reply-To: <CAEs=z9Pajgjnq56+umA+g9-NFv-Rzo9m5sa-7cow_byckLiJ0A@mail.gmail.com>

Hi Ross,

Welcome to the list and thanks for reporting your findings. I haven't
looked at all at the first issue you brought up, about the protocol-v2
doc.

On Sat, 19 Dec 2020 at 18:10, Ross Light <ross@zombiezen.com> wrote:
> 2. In the pack-format doc, the Deltified representation section [2]
> describes the instruction sequence well, but neglects to mention the
> two size varints [3] at the beginning of such an object.

Would something like this be what you have in mind?

Martin Ågren (2):
  pack-format.txt: define "varint" format
  pack-format.txt: document lengths at start of delta data

 Documentation/technical/pack-format.txt | 22 +++++++++++++++++-----
 1 file changed, 17 insertions(+), 5 deletions(-)

-- 
2.30.0.rc1


  reply	other threads:[~2020-12-21  7:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-19 17:07 Documentation errors for HTTP protocol v2 and packfile Ross Light
2020-12-21  7:54 ` Martin Ågren [this message]
2020-12-21  7:54   ` [PATCH 1/2] pack-format.txt: define "varint" format Martin Ågren
2020-12-21 21:40     ` Junio C Hamano
2020-12-29 22:41       ` Martin Ågren
2020-12-21  7:54   ` [PATCH 2/2] pack-format.txt: document lengths at start of delta data Martin Ågren
2020-12-23  4:40   ` [PATCH 0/2] " Ross Light
2020-12-29 22:43   ` [PATCH v2] pack-format.txt: document sizes " Martin Ågren

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cover.1608537234.git.martin.agren@gmail.com \
    --to=martin.agren@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=ross@zombiezen.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).