git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Farhan Khan <farhan@farhan.codes>
To: git@vger.kernel.org
Subject: How crc32 value is calculated for deltified objects
Date: Sat, 2 Mar 2019 17:08:35 -0500	[thread overview]
Message-ID: <20190302220835.GA12793@pc.farhan.codes> (raw)

[-- Attachment #1: Type: text/plain, Size: 637 bytes --]

Hi all,

I am trying to figure out how the crc32 value is calculated for deltified
objects.

It appears that the crc32 value is updated in the use() function. After
calculating the header, the unpack_raw_entry() function will call
unpack_entry_data(). This function inflates the delta object and calls use().

My question is, does it update the crc32 value with the deltas or just the
undeltified object? And if my question implies I do not understand how this
process works, can you please explain to me how the crc32 value is constructed?

Thank you.
---
Farhan Khan
PGP Fingerprint: 1312 89CE 663E 1EB2 179C  1C83 C41D 2281 F8DA C0DE

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

                 reply	other threads:[~2019-03-02 22:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20190302220835.GA12793@pc.farhan.codes \
    --to=farhan@farhan.codes \
    --cc=git@vger.kernel.org \
    /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).