From: Jeff King <peff@peff.net>
To: Eric Wong <e@80x24.org>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: Thank you for public-inbox!
Date: Thu, 30 Aug 2018 04:19:45 -0400 [thread overview]
Message-ID: <20180830081945.GB10224@sigill.intra.peff.net> (raw)
In-Reply-To: <20180830072049.dgsjn3537xzo6qcm@dcvr>
On Thu, Aug 30, 2018 at 07:20:49AM +0000, Eric Wong wrote:
> > At the very least, I think if we plan to reference without an http URL
> > that we would use something like URI-ish, like <mid:ABC@XYZ>. That gives
> > tools a better chance to say "OK, I know how to find message-ids"
> > (though I still think that it's much less helpful out of the box
> > compared to an http URL).
>
> That would be awesome if somelike like <mid:ABC@XYZ> could be a
> standard and adopted (likewise with <git:$object_id>).
>
> I haven't checked, but are there existing/similar RFCs?
> Surely somebody has tried to get <git:$object_id>
> adopted by now, right?
There's https://tools.ietf.org/html/rfc2392. They even call it "mid:". :)
I don't know of any git URI scheme, though it's similar in spirit to
magnet: links. Those are a bit verbose, though, because they're really a
meta-format for a bunch of different content-addressable schemes.
-Peff
prev parent reply other threads:[~2018-08-30 8:19 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
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 [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: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180830081945.GB10224@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=e@80x24.org \
--cc=git@vger.kernel.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/mirrors/git.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).