git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: public inbox links, was: Re: preserve untracked cache, was Re: What's cooking in git.git (Jun 2017, #01; Thu, 1)

From
EWEric Wong <e@80x24.org>
Date
Jun 3, 2017, 01:24 UTC
Message-ID
<20170603012449.GA20194@dcvr>
In-Reply-To
<CAGZ79kboxyUKy2j2GDZzWhOHeLHM17fYhQ0Wy=HxKaM-zXFC3A@mail.gmail.com>
Stefan Beller <sbeller@google.com> wrote:
> Today I learned again how public-inbox is awesome! Thanks Eric!
You're welcome :)
> * You can just copy the message ID INCLUDING the surrounding < >
>   and public inbox still just shows you the correct message. I had assumed
>   you would need to strip off the < > and I did so since.

Yeah, it's a fallback since it's probably a common mistake. AFAIK, git-send-email also avoids redundantly adding '<>' and only adds them if necessary.

> On Fri, Jun 2, 2017 at 5:26 PM, Junio C Hamano <gitster@pobox.com> wrote:
<snip>
Show 6 quoted lines
> > Issue #01 of June reports it in 'master':
> > https://public-inbox.org/git/<xmqqshjk5ezb.fsf@gitster.mtv.corp.google.com>
>
> * However with the < > unstripped, the awesomeness is limited:
>   Some tools (including my mail reader as well as public inbox itself[1])
>   do not recognize the link when there are < > in there.

Yeah, that's actually bad form on Junio's part. public-inbox can only support it up to an extent...

I seem to recall seeing some standard or style recommendation that URLs (of any type) be surrounded by angle brackets in text:

<https://public-inbox.org/git/xmqqshjk5ezb.fsf@gitster.mtv.corp.google.com/>

So public-inbox (and other parsers) should stop looking for URLs outside of the '<>'

But I think the newer style manuals state having spaces around the URL is enough.

Show 5 quoted lines
> While the second point is not the end of the world, it's still
> slightly annoying,
> which is why I thought I'll point it out here.
> 
> [1] https://public-inbox.org/git/xmqqvaodx6g4.fsf@gitster.mtv.corp.google.com/
Previous: Stefan Beller
Message 2 of 2 in “public inbox links, was: Re: preserve untracked cache, was Re: What's cooking in git.git (Jun 2017, #01; Thu, 1)”
  1. Stefan BellerJun 3, 2017
  2. Eric WongJun 3, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.