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

Re: [PATCH] More flexible URL patterns for gitweb

From
DTDamien Tournoud <damien@tournoud.net>
Date
Apr 11, 2010, 17:46 UTC
Message-ID
<r2te821df551004111046v2ef3219x5c012af27f2cc974@mail.gmail.com>
In-Reply-To
<m37hodhp3e.fsf@localhost.localdomain>
On Sun, Apr 11, 2010 at 7:33 PM, Jakub Narebski <jnareb@gmail.com> wrote:
Show 9 quoted lines
> To not break backward compatibility, wouldn't it be better to check if
> elements of @git_base_url_list end with ':' or '/', and join base with
> project path depending on this condition, i.e.:
>
> +       @url_list = map { m/[/:]$/ ? "$_$project" : "$_/$project" } @git_base_url_list
> +               unless @url_list;
>
> This means: if base ends with colon ':' or slash '/', concatenate base
> and project path, otherwise join them using '/' as field separator.
Thanks for the review. Indeed this way sounds better.

All this is new to me so I'm not sure what is the way forward. Should I publish another patch or would you?

Damien Tournoud
Previous: Jakub NarebskiNext: Jakub Narebski
Message 3 of 4 in “More flexible URL patterns for gitweb”
  1. More flexible URL patterns for gitwebDamien Tournoud, Apr 11, 2010
  2. Jakub NarebskiApr 11, 2010
  3. Damien TournoudApr 11, 2010
  4. Jakub NarebskiApr 11, 2010

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.