From: Graham Perrin <grahamperrin@freebsd.org>
To: cgit@lists.zx2c4.com
Subject: Re: Angle brackets - < and >
Date: Fri, 23 Sep 2022 06:55:06 +0100 [thread overview]
Message-ID: <6a88fcac-f043-6c48-2f03-5aa2e1f65ea6@freebsd.org> (raw)
In-Reply-To: <YyXr+pL5L6htt5z0@keeping.me.uk>
[-- Attachment #1.1: Type: text/plain, Size: 1223 bytes --]
On 17/09/2022 16:47, John Keeping wrote:
> On Sat, Sep 17, 2022 at 03:32:48PM +0100, Graham Perrin wrote:
>> Commit messages
>> <https://github.com/freebsd/freebsd-doc/commit/f814150c1af932259a239ad01c0237f58bdce402>
>> and
>> <https://github.com/freebsd/freebsd-doc/commit/9d5951404e425725a84265113abef1c3b2e86d91>
>> appear OK.
>>
>> In corresponding
>> <https://cgit.freebsd.org/doc/commit/?id=f814150c1af932259a239ad01c0237f58bdce402>
>> and
>> <https://cgit.freebsd.org/doc/commit/?id=9d5951404e425725a84265113abef1c3b2e86d91>,
>> it's as if the closing angle bracket is misinterpreted as part of the
>> address.
>>
>> Please, might this be a bug in cgit?
> Commit message formatting in CGit is extensible and the example filter
> shipped with CGit does not do any URL detection, so cgit.freebsd.org
> must be using their own filter.
>
> I suggest you report a bug to them.
>
>
> Regards,
> John
Thank you.
From a commit today, it seems that white space delimitation is
similarly affected. FYI:
266473 – cgit.freebsd.org breaks some links – seems to not recognise
some types of URI delimiter (RFC 3986)
<https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266473>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
prev parent reply other threads:[~2022-09-23 5:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-17 14:32 Graham Perrin
2022-09-17 15:47 ` John Keeping
2022-09-23 5:55 ` Graham Perrin [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6a88fcac-f043-6c48-2f03-5aa2e1f65ea6@freebsd.org \
--to=grahamperrin@freebsd.org \
--cc=cgit@lists.zx2c4.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 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 NNTP newsgroup(s).