Hi!
On Sun, 2022-09-18 at 21:42:37 -0700, Russ Allbery wrote:
> "Daniel Shahaf" writes:
> > Here's a revision of the patch incorporating the feedback so far:
>
> Thank you for this patch! I confirmed that your description matches the
> regular expression. This has now been applied for the
"Daniel Shahaf" writes:
> Here's a revision of the patch incorporating the feedback so far:
Thank you for this patch! I confirmed that your description matches the
regular expression. This has now been applied for the next release of
Debian Policy.
> [[[
> diff --git a/policy/ch-source.rst
Guillem Jover wrote on Sat, 14 Mar 2020 22:51 +00:00:
> Hi!
>
> On Sat, 2020-03-14 at 21:49:12 +, Daniel Shahaf wrote:
> > Sean Whitton wrote on Sat, 14 Mar 2020 20:39 +00:00:
> > > On Sat 14 Mar 2020 at 08:09PM +00, Daniel Shahaf wrote:
> > > > Daniel Shahaf wrote on Sat, 14 Mar 2020 18:14
Hi!
On Sat, 2020-03-14 at 21:49:12 +, Daniel Shahaf wrote:
> Sean Whitton wrote on Sat, 14 Mar 2020 20:39 +00:00:
> > On Sat 14 Mar 2020 at 08:09PM +00, Daniel Shahaf wrote:
> > > Daniel Shahaf wrote on Sat, 14 Mar 2020 18:14 +00:00:
> > >> - ::
> > >> -
> > >> -
Hello,
On Sat 14 Mar 2020 at 09:49PM +00, Daniel Shahaf wrote:
> I agree that it is probably incorrect, but that doesn't follow from the
> semantics of /\s/. Even if /\s/ matched any single byte/character, the
> semantics would still depend on what haystack the regexp is matched
> against: the
Sean Whitton wrote on Sat, 14 Mar 2020 20:39 +00:00:
> Hello,
>
> On Sat 14 Mar 2020 at 08:09PM +00, Daniel Shahaf wrote:
>
> > Daniel Shahaf wrote on Sat, 14 Mar 2020 18:14 +00:00:
> >> - ::
> >> -
> >> - /closes:\s*(?:bug)?\#?\s?\d+(?:,\s*(?:bug)?\#?\s?\d+)*/i
> >> -
> >> + All of
Hello,
On Sat 14 Mar 2020 at 08:09PM +00, Daniel Shahaf wrote:
> Daniel Shahaf wrote on Sat, 14 Mar 2020 18:14 +00:00:
>> - ::
>> -
>> - /closes:\s*(?:bug)?\#?\s?\d+(?:,\s*(?:bug)?\#?\s?\d+)*/i
>> -
>> + All of the bug numbers listed must be given on the same physical line
>> + as
Hello,
On Sat 14 Mar 2020 at 07:50PM +00, Daniel Shahaf wrote:
> What shape would this take? Would the Perl definition be authoritative
> and the English one informative, or vice versa? (Or something else
> altogether?)
Well, firstly, we're talking about the contents of a footnote here, so
Daniel Shahaf wrote on Sat, 14 Mar 2020 18:14 +00:00:
> - ::
> -
> - /closes:\s*(?:bug)?\#?\s?\d+(?:,\s*(?:bug)?\#?\s?\d+)*/i
> -
> + All of the bug numbers listed must be given on the same physical line
> + as the word ``closes:``.
Is this newly-added sentence correct?
Whether it
Sean Whitton wrote on Sat, 14 Mar 2020 19:06 +00:00:
> Hello Daniel,
>
> On Sat 14 Mar 2020 at 06:14PM +00, Daniel Shahaf wrote:
>
> > The documentation of the "Closes: #NN" changelog syntax describes
> > the syntax in terms of a Perl regular expression. However, not all
> > readers know
Hi Daniel,
On Sat, Mar 14, 2020 at 06:14:02PM +, Daniel Shahaf wrote:
> The documentation of the "Closes: #NN" changelog syntax describes
> the syntax in terms of a Perl regular expression. However, not all
> readers know Perl. I suggest to describe the semantics in English,
> in
Package: debian-policy
Version: 4.5.0.0
Severity: wishlist
Tags: patch upstream
Dear Maintainer,
The documentation of the "Closes: #NN" changelog syntax describes
the syntax in terms of a Perl regular expression. However, not all
readers know Perl. I suggest to describe the semantics in
12 matches
Mail list logo
