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

Re: [PATCH v2] userdiff: remove empty subexpression from elixir regex

From
Ed Maste <emaste@freebsd.org>
Date
Dec 13, 2019, 15:58 UTC
Message-ID
<CAPyFy2B_P7qJ+ocg8rzNWEZWo2uKzaZsfYRvvhwUbAXv2AB6pg@mail.gmail.com>
In-Reply-To
<0c9d891e-382f-03d1-bcbd-d652f1d58f4d@kdbg.org>
On Fri, 13 Dec 2019 at 14:24, Johannes Sixt <j6t@kdbg.org> wrote:
Show 10 quoted lines
>
> Am 13.12.19 um 18:55 schrieb Ed Maste:
> > The regex failed to compile on FreeBSD.
> >
> > Fixes: a807200f67588f6e
>
> Having a references is this form is unusual for our codebase. (Not that
> I mind a lot, though.) I expect that Junio will commit the fix on top of
> the commit that introduced the bogus regex anyway (branch
> ln/userdiff-elixir), and then it will be easy find.
Ok, I picked this up from the Linux kernel where someone added a
Fixes: tag to one of my changes (which had the hash of the original
change as part of the commit message body).
Show 6 quoted lines
> > Signed-off-by: Ed Maste <emaste@FreeBSD.org>
> > ---
> > Add /* -- */ to make things more clear and be consistent with other
> > patterns.
>
> This text would be nice to have in the commit message.

Ah, I didn't think it was remarkable (it's consistent with all of the existing entries) but the change is indeed broader than what the commit message implies. I'm happy to send a v3 with an amended commit message if that's desired.

Previous: Johannes SixtNext: Junio C Hamano
Message 7 of 10 in “userdiff: remove empty subexpression from elixir regex”
  1. userdiff: remove empty subexpression from elixir regexEd Maste, Dec 13, 2019
  2. Jeff KingDec 13, 2019
  3. Ed MasteDec 13, 2019
  4. userdiff: remove empty subexpression from elixir regexEd Maste, Dec 13, 2019
  5. Jeff KingDec 13, 2019
  6. Johannes SixtDec 13, 2019
  7. Ed MasteDec 13, 2019
  8. Junio C HamanoDec 13, 2019
  9. Numbers with specific base (was: [PATCH] userdiff: remove empty subexpression from elixir regex)Achim Gratz, Dec 13, 2019
  10. Junio C HamanoDec 13, 2019

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.