public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ulrich Mueller <ulm@gentoo.org>
To: Arthur Zamarin <arthurzam@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org,  glep@gentoo.org
Subject: Re: [gentoo-dev] Re: [DRAFT v2] GLEP 84: Standard format for package.mask files
Date: Fri, 13 Oct 2023 21:46:59 +0200	[thread overview]
Message-ID: <uv8baqp8s@gentoo.org> (raw)
In-Reply-To: <1aee1edd-2e5f-4aae-8b1a-604fa6b881f5@gentoo.org> (Arthur Zamarin's message of "Fri, 13 Oct 2023 22:35:45 +0300")

[-- Attachment #1: Type: text/plain, Size: 653 bytes --]

>>>>> On Fri, 13 Oct 2023, Arthur Zamarin wrote:

>> Make this one either "[Bb]ugs? #\d+(,? #\d+)*" (which I'd prefer)
>> or "[Bb]ugs? +#\d+(,? +#\d+)*". That is, same number of spaces in both
>> locations.

> OK, would be hard to define it correctly in the BNF, but will just use
> {n} syntax to pass the intent, and explain in English what you said here
> (same amount of spaces between "things", with preferred n=1.

I think you've misunderstood me. I meant that the regex should either
match exactly one space, but then in both places (after "[Bb]ugs?" and
after the comma). Or, it should allow an arbitrary number of spaces
in both places.

Ulrich

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 507 bytes --]

  reply	other threads:[~2023-10-13 19:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-13 14:11 [gentoo-dev] [DRAFT v2] GLEP 84: Standard format for package.mask files Arthur Zamarin
2023-10-13 16:06 ` [gentoo-dev] " Ulrich Mueller
2023-10-13 16:30   ` Arthur Zamarin
2023-10-13 18:42     ` Ulrich Mueller
2023-10-13 19:35       ` Arthur Zamarin
2023-10-13 19:46         ` Ulrich Mueller [this message]
2023-10-13 18:49 ` [gentoo-dev] " Ulrich Mueller
2023-10-13 19:32   ` Arthur Zamarin
2023-10-13 19:43     ` Ulrich Mueller

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=uv8baqp8s@gentoo.org \
    --to=ulm@gentoo.org \
    --cc=arthurzam@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=glep@gentoo.org \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox