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

2 messages from 2017-06-03 to 2017-06-03. Participants: Stefan Beller, Eric Wong.
Thread: https://gitlist.dev/t/46104

## Stefan Beller, 2017-06-03 00:46

Subject: public inbox links, was: Re: preserve untracked cache, was Re: What's cooking in git.git (Jun 2017, #01; Thu, 1)
Message-ID: <CAGZ79kboxyUKy2j2GDZzWhOHeLHM17fYhQ0Wy=HxKaM-zXFC3A@mail.gmail.com>
URL: https://gitlist.dev/e/CAGZ79kboxyUKy2j2GDZzWhOHeLHM17fYhQ0Wy%3DHxKaM-zXFC3A%40mail.gmail.com

```
On Fri, Jun 2, 2017 at 5:26 PM, Junio C Hamano <gitster@pobox.com> wrote:
>
> Issue #06 of May marked it to be merged to 'next':
> https://public-inbox.org/git/<xmqqo9ulo1yn.fsf@gitster.mtv.corp.google.com>
>
> Issue #07 of May marked it for 'master':
> https://public-inbox.org/git/<xmqqwp98j8q2.fsf@gitster.mtv.corp.google.com>
>
> Issue #08 of May kept it (i.e. no issues discovered in the
> meantime):
> https://public-inbox.org/git/<xmqq1sr889lb.fsf@gitster.mtv.corp.google.com>
>
> Issue #01 of June reports it in 'master':
> https://public-inbox.org/git/<xmqqshjk5ezb.fsf@gitster.mtv.corp.google.com>
>

Today I learned again how public-inbox is awesome! Thanks Eric!

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

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

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/

Thanks,
Stefan

```

## Eric Wong, 2017-06-03 01:24

Subject: Re: public inbox links, was: Re: preserve untracked cache, was Re: What's cooking in git.git (Jun 2017, #01; Thu, 1)
Message-ID: <20170603012449.GA20194@dcvr>
URL: https://gitlist.dev/e/20170603012449.GA20194%40dcvr
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>
> > 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.

> 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/

```