From: Simon Marchi <simon.marchi@polymtl.ca>
To: Mark Wielaard <mark@klomp.org>, "Frank Ch. Eigler" <fche@elastic.org>
Cc: Overseers mailing list <overseers@sourceware.org>
Subject: Re: inbox.sourceware.org experiment
Date: Thu, 18 Aug 2022 10:40:00 -0400 [thread overview]
Message-ID: <3ed574a5-e539-158e-2102-0d6aa4ec4ae8@polymtl.ca> (raw)
In-Reply-To: <Yv5DvkMnDvS7wdIW@wildebeest.org>
On 8/18/22 09:50, Mark Wielaard wrote:
> I am not sure that is my main interest in public-inbox, but yes, I do
> really like public-inbox because it allows tools like b4 (which I have
> already tested against our instance) and piem (not tested yet) to
> easily pick up and apply patch emails.
> https://git.kernel.org/pub/scm/utils/b4/b4.git/tree/README.rst
> https://docs.kyleam.com/piem/
>
> I think others will also use those (or similar) tools. But I primarily
> expect users to use the public-inbox archives as a way to access the
> mailinglists without having to subscribe, but still be able to easily
> get the actual (raw) messages (either through git, atom, mbox, nntp or
> imap) to follow the conversations. Which I think is the main
> interesting thing public-inbox offers.
For me it's:
- Being able to download the raw emails in order to apply patches or to
properly reply to messages on lists I'm not subscribed to
- I never thought about the feature Mark mentioned, about download an
mbox for a given query. But if you want to download a very long
patch series to apply it locally, it could be useful.
- Better display and browsing to read longer threads that span multiple
months. For example, trying to follow this thread on Mailman would
be complicated:
https://inbox.sourceware.org/gdb-patches/20220428033542.1636284-1-simon.marchi@polymtl.ca/T/#r5f31e373eeb958095add41686e0ae7d1dcac9f1a
- Search: I find it useful to be able to find a message by Message-ID.
For instance, I'm reading the message in my client, and I want to
send someone the link to that message in the web interface. In my
instance (pi.simark.ca) I can paste the Message-ID in the search box
and it gets me directly to the right message. On
inbox.sourceware.org, I don't see the same search box, maybe it is
because of the V1/V2 thing you have been talking about?
- Not super important, but I like that the URLs to messages contain the
Message-IDs. This way, in a distant future where
inbox.sourceware.org does not exist anymore, someone with the archive
can still find out which message a given URL refers to. A bit like
if I give you this URL:
https://gitlab.com/gnutools/binutils-gdb/-/commit/243cf0f69c36c4ee09c3c2b0bc7a97dc16119c51
and Gitlab does not exist anymore, you can still find you which
commit I am talking about if you have a copy of the binutils-gdb git
repo.
Also, you were talking about space. If you want to save some space, I
don't think it's very useful to have the *-cvs lists on there. And
there are lists that are pretty much dead that you could skip too.
Simon
next prev parent reply other threads:[~2022-08-18 14:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-13 14:14 Mark Wielaard
2022-08-15 13:00 ` Mark Wielaard
2022-08-16 21:36 ` Mark Wielaard
2022-08-16 22:10 ` Frank Ch. Eigler
2022-08-17 12:25 ` Mark Wielaard
2022-08-17 13:24 ` Frank Ch. Eigler
2022-08-17 21:18 ` Mark Wielaard
2022-08-17 21:33 ` Frank Ch. Eigler
2022-08-18 13:50 ` Mark Wielaard
2022-08-18 14:40 ` Simon Marchi [this message]
2022-08-21 17:41 ` Mark Wielaard
2022-08-23 20:15 ` Mark Wielaard
2022-08-23 22:08 ` Mark Wielaard
2022-08-24 10:05 ` Mark Wielaard
2022-08-24 21:06 ` Mark Wielaard
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=3ed574a5-e539-158e-2102-0d6aa4ec4ae8@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=fche@elastic.org \
--cc=mark@klomp.org \
--cc=overseers@sourceware.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).