unofficial mirror of meta@public-inbox.org
 help / color / mirror / Atom feed
From: Eric Wong <e@80x24.org>
To: Jeff King <peff@peff.net>
Cc: Jonathan Nieder <jrnieder@gmail.com>, meta@public-inbox.org
Subject: Re: Contributing messages to an archive
Date: Tue, 3 Jul 2018 21:08:34 +0000	[thread overview]
Message-ID: <20180703210834.GB15579@dcvr> (raw)
In-Reply-To: <20180703210023.GA14211@sigill.intra.peff.net>

Jeff King <peff@peff.net> wrote:
> On Tue, Jul 03, 2018 at 01:44:00PM -0700, Jonathan Nieder wrote:
> > 
> > Is there a way to configure the search to look at multiple archives?
> 
> Yeah, that was my main impetus in putting them in the vger archive.
> Those messages _would_ have gone to the list, if not for the embargo,
> and ideally people digging into the history later would be able to find
> them easily (either by message-id if referenced, or by keyword
> searching).

Yes, at least by Message-ID references it already finds a message
on the same server.  So Jonathan's original message to this list
using /git/:

https://public-inbox.org/git/20180703160910.GB51821@aiede.svl.corp.google.com/
https://public-inbox.org/git/20180703160910.GB51821@aiede.svl.corp.google.com/

...refers the reader to the archive for this list:

https://public-inbox.org/meta/20180703160910.GB51821@aiede.svl.corp.google.com/

(It needed to work that way for NNTP).


Dealing with the UI and configuration for search ends up being a
bit tougher...

  reply	other threads:[~2018-07-03 21:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-03 16:09 Contributing messages to an archive Jonathan Nieder
2018-07-03 16:39 ` 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 [this message]
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=20180703210834.GB15579@dcvr \
    --to=e@80x24.org \
    --cc=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).