From: Gregory Heytings <gregory@heytings.org>
To: Tassilo Horn <thorn+gnu@fastmail.fm>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
miha@kamnitnik.top, 51316@debbugs.gnu.org
Subject: bug#51316: 29.0.50; Should we match the final ".git" in bug-reference autosetup?
Date: Sat, 23 Oct 2021 12:58:55 +0000 [thread overview]
Message-ID: <2d6e9fbc47ba47bac7fa@heytings.org> (raw)
In-Reply-To: <8735osayjm.fsf@gnu.org>
>
> I've also tried, and it seems the maximum number of trailing slashes is
> two. Those all work:
>
> https://github.com/djcb/mu
> https://github.com/djcb/mu/
> https://github.com/djcb/mu//
> https://github.com/djcb/mu.git
> https://github.com/djcb/mu.git/
> https://github.com/djcb/mu.git//
>
> but any more / gives me "Not found". Well, and I guess even the two-/
> will most probably never occur in real-life when considering where the
> URL comes from. I mean, those are usually copy-and-pasted from the
> forge's special "clone me" button or from a browser's URL bar.
>
Allowing more trailing slashes is a convenience that some but not all Git
hosts offer. On Gitlab an (unlimited?) number of trailing slashes are
allowed, on Github it's two, on Savannah it's one. The safest solution is
probably to allow either a trailing ".git" or a trailing ".git/".
next prev parent reply other threads:[~2021-10-23 12:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-21 12:18 bug#51316: 29.0.50; Should we match the final ".git" in bug-reference autosetup? miha--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-22 14:59 ` Lars Ingebrigtsen
2021-10-22 20:45 ` Tassilo Horn
2021-10-22 21:42 ` miha--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-23 9:12 ` Tassilo Horn
2021-10-23 12:58 ` Gregory Heytings [this message]
2021-10-24 12:17 ` Lars Ingebrigtsen
2021-10-26 9:01 ` miha--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-27 13:02 ` Lars Ingebrigtsen
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=2d6e9fbc47ba47bac7fa@heytings.org \
--to=gregory@heytings.org \
--cc=51316@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=miha@kamnitnik.top \
--cc=thorn+gnu@fastmail.fm \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.