From: Eric Wong <e@80x24.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: meta@public-inbox.org
Subject: Re: internal format (was: Relationship between public-inbox and ssoma?)
Date: Thu, 15 Mar 2018 16:40:12 +0000 [thread overview]
Message-ID: <20180315164012.GA20246@whir> (raw)
In-Reply-To: <jwv1sgl5php.fsf-monnier+inbox.comp.mail.public-inbox.meta@gnu.org>
Stefan Monnier <monnier@IRO.UMontreal.CA> wrote:
> > The work-in-progress "v2" public-inbox format diverges and I
> > don't currently have plans to port ssoma to use it. The v1
> > format will remain supported in public-inbox.
>
> Which reminds me: do you have some document that explains the reasoning
> behind the choice of format (especially which alternatives were
> considered and dropped and why)?
v1 or v2? Some of the reasoning for v2 was here:
https://public-inbox.org/meta/20180209205140.GA11047@dcvr/
v1 was similar to what git did with loose objects and prevented
dupes based on Message-ID. That worked well enough for small
non-mirror lists and wasn't designed with search (Xapian) in mind.
As for git itself: reliability, ease-of-replication, storage
efficiency.
next prev parent reply other threads:[~2018-03-15 16:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-05 0:54 Relationship between public-inbox and ssoma? Nicolás Ojeda Bär
2018-03-05 2:07 ` Eric Wong
2018-03-05 11:45 ` Nicolás Ojeda Bär
2018-03-05 17:50 ` Eric Wong
2018-03-05 18:06 ` Nicolás Ojeda Bär
2018-03-19 7:43 ` watch performance [was: Relationship between public-inbox and ssoma?] Eric Wong
2018-03-15 15:30 ` internal format (was: Relationship between public-inbox and ssoma?) Stefan Monnier
2018-03-15 16:40 ` Eric Wong [this message]
2018-03-15 18:49 ` internal format Stefan Monnier
2018-03-15 20:14 ` Eric Wong
2018-03-15 21:05 ` Stefan Monnier
2018-03-15 21:21 ` 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=20180315164012.GA20246@whir \
--to=e@80x24.org \
--cc=meta@public-inbox.org \
--cc=monnier@IRO.UMontreal.CA \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/public-inbox.git
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).