From: Eric Wong <e@80x24.org>
To: Veronika Kabatova <vkabatov@redhat.com>
Cc: Daniel Axtens <dja@axtens.net>,
Dmitry Vyukov <dvyukov@google.com>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
workflows@vger.kernel.org, automated-testing@yoctoproject.org,
Brendan Higgins <brendanhiggins@google.com>,
Han-Wen Nienhuys <hanwen@google.com>,
Kevin Hilman <khilman@baylibre.com>
Subject: Re: Structured feeds
Date: Fri, 8 Nov 2019 00:24:38 +0000 [thread overview]
Message-ID: <20191108002438.GA7590@dcvr> (raw)
In-Reply-To: <1033825454.8368196.1573125977348.JavaMail.zimbra@redhat.com>
Veronika Kabatova <vkabatov@redhat.com> wrote:
> I'll be totally honest and admit I ignored most of the implementation details
> of public inbox feeds (will take a look when I have some free time) but as
> long as they contain the original email, the feature should be usable with
> them too.
Implementation details should not matter to consumers.
public-inbox exposes everything as NNTP which is the same
message format as email. NNTP is also much more stable and
established than the v2 git layout of public-inbox (which could
be superceded by a hypothetical "v3" layout).
I highly recommend anybody consuming public-inbox (and not
making 1:1 mirrors) use NNTP since it's well-established
and doesn't enforce long-term storage requirements.
I hope to support HTTP(S) CONNECT tunneling as a means for users
behind firewalls to get around NNTP port 119/563 restrictions.
next prev parent reply other threads:[~2019-11-08 0:24 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 10:02 Structured feeds Dmitry Vyukov
2019-11-06 15:35 ` Daniel Axtens
2019-11-06 20:50 ` Konstantin Ryabitsev
2019-11-07 9:08 ` Dmitry Vyukov
2019-11-07 10:57 ` Daniel Axtens
2019-11-07 11:26 ` Veronika Kabatova
2019-11-08 0:24 ` Eric Wong [this message]
2019-11-07 11:09 ` Daniel Axtens
2019-11-08 14:18 ` Daniel Axtens
2019-11-09 7:41 ` Johannes Berg
2019-11-12 10:44 ` Daniel Borkmann
[not found] ` <208edf06eb4c56a4f376caf0feced65f09d23f93.camel@that.guru>
2019-11-30 18:16 ` Johannes Berg
2019-11-30 18:36 ` Stephen Finucane
2019-11-07 8:53 ` Dmitry Vyukov
2019-11-07 10:40 ` Daniel Axtens
2019-11-07 10:43 ` Dmitry Vyukov
2019-11-07 20:43 ` [Automated-testing] " Don Zickus
2019-11-08 7:58 ` Dmitry Vyukov
2019-11-08 15:26 ` Don Zickus
2019-11-08 11:44 ` Daniel Axtens
2019-11-08 14:54 ` Don Zickus
2019-11-06 19:54 ` Han-Wen Nienhuys
2019-11-06 20:31 ` Sean Whitton
2019-11-07 9:04 ` Dmitry Vyukov
2019-11-07 8:48 ` [Automated-testing] " Tim.Bird
2019-11-07 9:13 ` Dmitry Vyukov
2019-11-07 9:20 ` Tim.Bird
2019-11-07 20:53 ` Don Zickus
2019-11-08 8:05 ` Dmitry Vyukov
2019-11-08 14:52 ` Don Zickus
2019-11-11 9:20 ` Dmitry Vyukov
2019-11-11 15:14 ` Don Zickus
2019-11-12 22:54 ` Konstantin Ryabitsev
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=20191108002438.GA7590@dcvr \
--to=e@80x24.org \
--cc=automated-testing@yoctoproject.org \
--cc=brendanhiggins@google.com \
--cc=dja@axtens.net \
--cc=dvyukov@google.com \
--cc=hanwen@google.com \
--cc=khilman@baylibre.com \
--cc=konstantin@linuxfoundation.org \
--cc=vkabatov@redhat.com \
--cc=workflows@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).