From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: Re: [v2] introduction of content_id
Date: Thu, 22 Feb 2018 21:12:34 +0000 [thread overview]
Message-ID: <20180222211234.GA22833@dcvr> (raw)
In-Reply-To: <20180209181718.GA8847@dcvr>
Eric Wong <e@80x24.org> wrote:
> In addition to the git object_id (blob SHA-1) and Message-Id
> header; it seems necessary to introduce an in-between identifier
> for deduplicating which isn't as loose as Message-Id or as
> strict as object_id: content_id
I think this will only be calculated-on-the-fly in cases the
Message-ID matches. No need to cement it into the Xapian DB,
meaning we can tweak which headers we care about more freely.
prev parent reply other threads:[~2018-02-22 21:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 18:17 [v2] introduction of content_id Eric Wong
2018-02-09 19:40 ` Konstantin Ryabitsev
2018-02-09 20:11 ` Eric Wong
2018-02-22 21:12 ` Eric Wong [this message]
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
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180222211234.GA22833@dcvr \
--to=e@80x24.org \
--cc=meta@public-inbox.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 read-only IMAP folder(s) and NNTP newsgroup(s).