From: Eric Wong <e@80x24.org>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Samuel Lijin <sxlijin@gmail.com>,
Jonathan Tirado <tiradojonathan32@gmail.com>,
Jeff King <peff@peff.net>, Git Mailing List <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>,
Brandon Williams <bmwill@google.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
meta@public-inbox.org
Subject: Re: vger not relaying some of Junio's messages today?
Date: Sat, 6 May 2017 21:42:23 +0000 [thread overview]
Message-ID: <20170506214223.GA28534@starla> (raw)
In-Reply-To: <CACBZZX42rhmrq8z0u1aRXw87oT22YywwnaFHUMjDYgtE_i56nw@mail.gmail.com>
Ævar Arnfjörð Bjarmason <avarab@gmail.com> wrote:
> Thanks a lot for public-inbox, my only problem with it is that it
> doesn't cover every single mailing list I'm on, just git :)
Yes, I'm hoping more folks can start running their own
instances. I notice you're on p5p where I started to
occasionally lurk a few years back. Is that something you'd be
interesting in mirroring? :)
Some lists I'm involved in tend to be centralized
(reply-to-list, not reply-to-all); so UI changes will be needed
in public-inbox...
> Are you or someone else maintaining some ancillary scripts for it? I
> probably need to fix my patch workflow but my usual mode is browsing
> in GMail & then manually 'git am'-ing some file I find with git-log
> commands.
Not really. I started out ssoma(*) just for archival/mirroring,
but it's mostly forgotten at this point. I would rather people
build on existing protocols like NNTP.
> I have one to git am a patch from a msgid, thought I should write
> something to handle a series in some DWIM fashion (e.g. apply the
> latest continuous sequence of patches matching --author) but figured
> that someone's probably wrote this already & I don't need to hack it
> up myself...
I've been meaning to wire up the web search to allow downloading
an entire mbox worth of search results. But it could be a bit
expensive for some queries and there needs to be a limit. The
current limit for web display is too small; so maybe 1000
messages per-mbox at a time to avoid DoS-ing the server.
(*) some-sort-of-mail archiver: git clone git://80x24.org/ssoma
next prev parent reply other threads:[~2017-05-06 21:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-06 17:46 vger not relaying some of Junio's messages today? Jonathan Tirado
2017-05-06 18:23 ` Samuel Lijin
2017-05-06 20:50 ` Eric Wong
2017-05-06 21:05 ` Ævar Arnfjörð Bjarmason
2017-05-06 21:42 ` Eric Wong [this message]
2017-05-08 10:42 ` Johannes Schindelin
2017-05-08 17:01 ` Brandon Williams
2017-05-09 10:10 ` Johannes Schindelin
2017-05-06 21:10 ` Samuel Lijin
2017-05-07 0:26 ` Eric Wong
2017-05-08 17:05 ` Brandon Williams
2017-05-07 1:05 ` Eric Wong
2017-05-07 3:00 ` Junio C Hamano
2017-05-07 3:24 ` Eric Wong
2017-05-07 12:41 ` Eric Wong
-- strict thread matches above, loose matches on Subject: below --
2017-01-27 3:57 Eric Wong
2017-01-27 4:01 ` Jeff King
2017-01-31 20:27 ` Junio C Hamano
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=20170506214223.GA28534@starla \
--to=e@80x24.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=avarab@gmail.com \
--cc=bmwill@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=meta@public-inbox.org \
--cc=peff@peff.net \
--cc=sxlijin@gmail.com \
--cc=tiradojonathan32@gmail.com \
/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 NNTP newsgroup(s).