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

Re: [PATCH] gitweb: Recognize *-to and Closes/Fixes trailers

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 25, 2020, 05:17 UTC
Message-ID
<xmqqeesc9m9l.fsf@gitster.c.googlers.com>
In-Reply-To
<20200425021723.16346-1-me@pluvano.com>
Emma Brooks <me@pluvano.com> writes:
> Commit trailers like "Thanks-to:", "Fixes:", and "Closes:" are fairly
> common, but gitweb didn't highlight them like other trailers.
Did you also sneak "cc" in without documenting/justifying?

When the re becomes this complex, it may not be a bad idea to switch to "/ ignore most whitespaces /x" style for readability.

> -		if ($line =~ m/^\s*([A-Z][-A-Za-z]*-[Bb]y|C[Cc]): /) {
> +		if ($line =~ m/^\s*([A-Z][-A-Za-z]*-([Bb]y|[Tt]o)|C[Cc]|(Clos|Fix)es): /) {
		if ($line =~ m/^\s*([A-Z][-A-Za-z]*-([Bb]y|[Tt]o) |
				    C[Cc] | Closes | Fixes ):\s /x) { 
Well, I am sloppy and did not make it all that easier to read.

More experienced Perl folks certainly would be able to teach us a much better convention to format things like this more readble.

Previous: Emma BrooksNext: Emma Brooks
Message 2 of 3 in “gitweb: Recognize *-to and Closes/Fixes trailers”
  1. gitweb: Recognize *-to and Closes/Fixes trailersEmma Brooks, Apr 25, 2020
  2. Junio C HamanoApr 25, 2020
  3. Emma BrooksApr 25, 2020

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.