GNU bug report logs - #51316
29.0.50; Should we match the final ".git" in bug-reference autosetup?

Previous Next

Full log

Message #24 received at 51316 <at> debbugs.gnu.org (full text, mbox):

From: Gregory Heytings <gregory <at> heytings.org>
To: Tassilo Horn <thorn+gnu <at> fastmail.fm>
Cc: Lars Ingebrigtsen <larsi <at> gnus.org>, miha <at> kamnitnik.top,
 51316 <at> debbugs.gnu.org
Subject: Re: bug#51316: 29.0.50; Should we match the final ".git" in
 bug-reference autosetup?
Date: Sat, 23 Oct 2021 12:58:55 +0000

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

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.