From: Jonathan Nieder <jrnieder@gmail.com>
To: meta@public-inbox.org
Cc: Jeff King <peff@peff.net>
Subject: Contributing messages to an archive
Date: Tue, 3 Jul 2018 09:09:10 -0700 [thread overview]
Message-ID: <20180703160910.GB51821@aiede.svl.corp.google.com> (raw)
Hi Eric et al,
I dug through the documentation at public-inbox.org and didn't see a
clear answer to this, so thought I'd ask to see whether my idea is
crazy.
https://public-inbox.org/git contains a copy of all messages sent to
the git mailing list, which is a useful resource for git developers.
But some messages don't reach there:
1. When vger has a bad day, some messages might not reach
public-inbox but they still reach any other developers that were
cc-ed
2. (My motivation) The git-security@googlegroups.com list receives
messages about embargoed issues that should not be made public
right away. We would like to switch to a model where after the
embargo expires, the discussion is made public.
Is there a way to inject messages into the public-inbox.org/git
archive? E.g. should I provide my own public-inbox style repository
to pull messages from, or is there an address that I can bounce
messages to?
Thanks,
Jonathan
next reply other threads:[~2018-07-03 16:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-03 16:09 Jonathan Nieder [this message]
2018-07-03 16:39 ` Contributing messages to an archive Jeff King
2018-07-03 19:54 ` Eric Wong
2018-07-03 20:44 ` Jonathan Nieder
2018-07-03 21:00 ` Jeff King
2018-07-03 21:08 ` Eric Wong
2018-07-03 21:03 ` 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=20180703160910.GB51821@aiede.svl.corp.google.com \
--to=jrnieder@gmail.com \
--cc=meta@public-inbox.org \
--cc=peff@peff.net \
/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).