From: Eric Wong <e@80x24.org>
To: git@vger.kernel.org
Subject: CFT: imaps://public-inbox.org/INBOX.comp.version-control.git.7
Date: Wed, 10 Jun 2020 18:41:47 +0000 [thread overview]
Message-ID: <20200610184147.GA1887@dcvr> (raw)
Hey all, I've been busy with public-inbox work this year.
I started working on a read-only IMAP/IMAPS server, and I expect
kernel.org to eventually host a v2 copy, too; and hopefully
other folks get interested in mirroring.
For now, you can access git@vger archives through 8 IMAP
mailboxes sliced into ~50K messages to not overload clients.
They go from 0..7, with 7 being the most recent:
imaps://public-inbox.org/INBOX.comp.version-control.git.0
imaps://public-inbox.org/INBOX.comp.version-control.git.1
imaps://public-inbox.org/INBOX.comp.version-control.git.2
imaps://public-inbox.org/INBOX.comp.version-control.git.3
imaps://public-inbox.org/INBOX.comp.version-control.git.4
imaps://public-inbox.org/INBOX.comp.version-control.git.5
imaps://public-inbox.org/INBOX.comp.version-control.git.6
imaps://public-inbox.org/INBOX.comp.version-control.git.7
When more messages show up,
imaps://public-inbox.org/INBOX.comp.version-control.git.8
should exist.
I've tested with mutt, offlineimap and mbsync (isync).
It's not yet complete (when is software ever?), but it's a
usable start, I think. Some more info about it over on
meta@public-inbox.org:
https://public-inbox.org/meta/20200609113442.GA16856@dcvr/
https://public-inbox.org/meta/20200610070519.18252-1-e@yhbt.net/
And maybe JMAP is coming, too...
next reply other threads:[~2020-06-10 18:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 18:41 Eric Wong [this message]
2020-06-10 23:31 ` CFT: imaps://public-inbox.org/INBOX.comp.version-control.git.7 Denton Liu
2020-06-11 0:30 ` Eric Wong
2020-06-16 7:08 ` Eric Wong
2020-06-16 13:19 ` Denton Liu
2020-06-23 18:08 ` CFT: imaps://public-inbox.org/INBOX.comp.version-control.git.8 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200610184147.GA1887@dcvr \
--to=e@80x24.org \
--cc=git@vger.kernel.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 NNTP newsgroup(s).