user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: Stefan Beller <sbeller@google.com>
Cc: Eric Wong <e@80x24.org>, meta@public-inbox.org
Subject: Re: Nonlinear history?
Date: Wed, 23 Aug 2017 16:06:51 -0400	[thread overview]
Message-ID: <20170823200651.gb7e5h3dywduxkrk@sigill.intra.peff.net> (raw)
In-Reply-To: <CAGZ79kYLcy_Pe0POUjUC+SaZYzFnLYhBYbY+ZNEBwc+32j8b1A@mail.gmail.com>

On Wed, Aug 23, 2017 at 11:29:24AM -0700, Stefan Beller wrote:

> Note that Peff seems to have build tooling around public-inbox
> (https://public-inbox.org/git/20170823154747.vxtyy2v2ofkxwrkx@sigill.intra.peff.net/)
> that would produce this precise lookup already.

It's not really built around public-inbox. I just like public-inbox URLs
because they use global identifiers, which means I can index them into
other systems.

My setup is basically maildir (backfilled from gmane long ago and kept
up to date with my subscription), indexed by mairix, and a script that
does m{https?:/public-inbox.org/git/(\S+)} on mail contents and and runs
"mairix m:$1" on the result.

It also looks for gmane.org URLs and runs

  gunzip -c ~/.gmane-to-mid.gz | grep "^${id}\$"

Not exactly high-tech, but it was easy to write and linear search is
good enough for personal use.

I used to do the same thing when gmane was up by resolving the article
numbers at gmane. But doing it without hitting the network is nicer
anyway, and of course the online method doesn't work anymore. :)

-Peff

      parent reply	other threads:[~2017-08-23 20:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-16 21:01 Nonlinear history? Stefan Beller
2017-08-23  1:42 ` Eric Wong
2017-08-23 18:29   ` Stefan Beller
2017-08-23 19:40     ` Eric Wong
2017-08-23 20:06     ` Jeff King [this message]

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=20170823200651.gb7e5h3dywduxkrk@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=e@80x24.org \
    --cc=meta@public-inbox.org \
    --cc=sbeller@google.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/public-inbox.git

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).