user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <>
To: Konstantin Ryabitsev <>
Subject: Re: [PATCH] TODO: notes about v2 format for giant archives
Date: Thu, 8 Feb 2018 03:09:51 +0000	[thread overview]
Message-ID: <20180208030951.GA10896@dcvr> (raw)
In-Reply-To: <>

Eric Wong <> wrote:
> +  * Ref rotation (splitting heads by YYYY or YYYY-MM)
> +
> +  * Support multiple git repos for a single archive?
> +    This seems gross, but splitting large packs in in git conflicts
> +    with bitmaps and we want to use both features.  Perhaps this
> +    limitation can be fixed in git instead of merely being documented:
> +

OK, so I've been strongly considering having git repos based on
YYYY or YYYY-MM because of shardability and ease-of-maintenance.

The other thing is I think we can support is subsystem lists
({netdev,fsdevel,stable}@vger) in the SAME git repo(s) with a
different head for each list.  That could make subsystem lists
cheaper to archive since there's a lot of overlap with the main

Headers like the List-Id:, Sender:, etc will still differ for
archival purposes and have different object_id in git; but git
should be able to delta well based on the rest of the message
based on age.

  reply	other threads:[~2018-02-08  3:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-16 22:36 Eric Wong
2018-02-08  3:09 ` Eric Wong [this message]
2018-02-08  4:05   ` Konstantin Ryabitsev
2018-02-08 17:08     ` Eric Wong

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:

  List information:

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

  git send-email \
    --in-reply-to=20180208030951.GA10896@dcvr \ \ \ \

* 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.
Code repositories for project(s) associated with this inbox:

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).