From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Andrei Rybak <rybak.a.v@gmail.com>
Cc: Eric Wong <e@80x24.org>, Jeff King <peff@peff.net>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
git@vger.kernel.org
Subject: Re: Thank you for public-inbox!
Date: Wed, 29 Aug 2018 18:30:50 +0200 [thread overview]
Message-ID: <871sahdtj9.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <3eb1c5e8-3e89-0d2e-30b1-339f38c4c703@gmail.com>
On Wed, Aug 29 2018, Andrei Rybak wrote:
> On 2018-08-29 12:02, Eric Wong wrote:
>> Anyways I hope to teach public-inbox to auto-linkify Message-ID-looking
>> strings "<XXXXXXXXXXX@XXXXXXXX>" into URLs for domain-portability,
>> (but it's ambiguous with email addresses). But yeah, I don't
>> like things being tied to domain names.
>
> This would be very useful for people who use MUAs without
> Message-ID lookup capabilities, even without domain-portability.
FWIW Many MUAs have some hidden way to do this, for example to find the
E-Mail I'm replying to (your E-Mail) on GMail:
https://mail.google.com/mail/u/0/#search/rfc822msgid%3A3eb1c5e8-3e89-0d2e-30b1-339f38c4c703%40gmail.com
I.e. rfc822msgid:<message-id>
Confusingly Google Groups accepts the same syntax, but will barf if you
include the <>'s, but that's from memory, maybe I misrecall or they've
fixed it.
next prev parent reply other threads:[~2018-08-29 16:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-27 14:25 Thank you for public-inbox! Johannes Schindelin
2018-08-27 17:31 ` Eric Wong
2018-08-29 5:07 ` Jeff King
2018-08-29 10:02 ` Eric Wong
2018-08-29 15:43 ` Andrei Rybak
2018-08-29 16:30 ` Ævar Arnfjörð Bjarmason [this message]
2018-08-30 3:30 ` Jeff King
2018-08-30 3:56 ` Jonathan Nieder
2018-08-30 7:20 ` Eric Wong
2018-08-31 1:14 ` Jonathan Nieder
2018-08-31 11:01 ` Eric Wong
2018-08-30 7:20 ` Eric Wong
2018-08-30 8:19 ` Jeff King
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=871sahdtj9.fsf@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=e@80x24.org \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=rybak.a.v@gmail.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.