From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: [PATCH] TODO: notes about v2 format for giant archives
Date: Wed, 7 Feb 2018 23:05:46 -0500 [thread overview]
Message-ID: <20180208040546.GA22174@gmail.com> (raw)
In-Reply-To: <20180208030951.GA10896@dcvr>
On Thu, Feb 08, 2018 at 03:09:51AM +0000, Eric Wong wrote:
> 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
> list.
Hmm... that's a pretty cool idea, but I wonder if people would find it
annoying to have to pull all the lkml-related objects if all they care
about are messages from, say, netdev. For archiving purposes I think it
would be great, but I'm less sure about UX impacts.
-K
next prev parent reply other threads:[~2018-02-08 4:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 22:36 [PATCH] TODO: notes about v2 format for giant archives Eric Wong
2018-02-08 3:09 ` Eric Wong
2018-02-08 4:05 ` Konstantin Ryabitsev [this message]
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:
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=20180208040546.GA22174@gmail.com \
--to=konstantin@linuxfoundation.org \
--cc=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).