user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: RFE: unified message-id lookup across all inboxes
Date: Tue, 8 Jan 2019 10:09:11 -0500	[thread overview]
Message-ID: <20190108150911.GB19908@pure.paranoia.local> (raw)
In-Reply-To: <20190108015420.GA28903@dcvr>

On Tue, Jan 08, 2019 at 01:54:20AM +0000, Eric Wong wrote:
> > It will tell you that the message is in another inbox (it was sent to
> > linux-arm-kernel and not cc'd to linux-kernel). The users don't like
> > that extra click, so they really just want a "show me the message if
> > it's anywhere on lore, and give me a link to marc.info, etc if not in
> > any of them).
> 
> Right.  I wanted to make it obvious to the user the message was
> in a different inbox.  So I think the new endpoint would be
> (without /$INBOX/ name):
> 
> 	http://$HTTP_HOST/_/$MESSAGE_ID
> 
> And 302 the user to the first message.

That sounds good to me.

> > It's been way too long since I've done Perl, which is why I'm not
> > offering patches, sorry! :)
> 
> No worries; I've got a bunch of other RFEs to take care of, too.
> 
> Also, I've been wondering if Ruby would have been a better
> language for this project?

I may be jaded from the times when Ruby's VM was really terrible, but
I'm still harbouring deep aversion to Ruby. I'll take Perl over Ruby any
day. :)

> Python doesn't fit my brain, Xapian bindings for Lua aren't yet
> in Debian, yet (RFP filed), but they're packaged for Ruby.  But
> I've been hacking on the Ruby VM for nearly a decade...  I just
> never get to use Ruby for development because I'm constantly
> side-tracked into fixing and attempting to improve the VM and
> language.  But VM hacking isn't really rewarding anymore, so I'm
> taking a break from that.

I don't think this is something that needs fixing. I expect it's easier
to just let people write custom web frontends to public-inbox
repositories (I suspect that's what LWN has done). In fact, I pondered
writing or commissioning a Django frontend if people needed more
shiny whizbang stuff out of the web interface, but kernel devs are the
kind of crowd that's served perfectly well by the current web frontend,
so I don't have a strong enough need to do anything there.

-K

  reply	other threads:[~2019-01-08 15:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-07 19:07 RFE: unified message-id lookup across all inboxes Konstantin Ryabitsev
2019-01-08  1:54 ` Eric Wong
2019-01-08 15:09   ` Konstantin Ryabitsev [this message]
2019-01-09  6:59     ` 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: http://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=20190108150911.GB19908@pure.paranoia.local \
    --to=konstantin@linuxfoundation.org \
    --cc=e@80x24.org \
    --cc=meta@public-inbox.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.
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).