On 23/09/2019 16:39, Austin Group Bug Tracker wrote:
--
(0004564) geoffclare (manager) - 2019-09-23 15:39
http://austingroupbugs.net/view.php?id=1234#c4564
A NOTE has been added to this issue.
==
http://austingroupbugs.net/view.php?id=1289
==
Reported By:joelsherrill
Assigned To:
The following issue has been SUBMITTED.
==
http://austingroupbugs.net/view.php?id=1293
==
Reported By:joelsherrill
Assigned To:
The following issue has been SUBMITTED.
==
http://austingroupbugs.net/view.php?id=1291
==
Reported By:joelsherrill
Assigned To:
The following issue has been SUBMITTED.
==
http://austingroupbugs.net/view.php?id=1292
==
Reported By:joelsherrill
Assigned To:
The following issue has been SUBMITTED.
==
http://austingroupbugs.net/view.php?id=1290
==
Reported By:joelsherrill
Assigned To:
The following issue has been SUBMITTED.
==
http://austingroupbugs.net/view.php?id=1289
==
Reported By:joelsherrill
Assigned To:
These are the draft minutes from yesterday's call. Andrew will need
to allocate the Austin-xxx document number and add the file to the
document register after he returns.
Regards,
Geoff.
---
Minutes of the 26 September 2019 Teleconference Austin-xxx Page 1 of 1
Submitted by Geoff
"Schwarz, Konrad" wrote:
> > -Original Message-
> > From: Robert Elz
>
> > So, is [[:"alpha":]] required to be treated the same as [[:alpha:]] , not
> > allowed to be treated the same,
> > explicitly unspecified, or simply never considered (previously) ?
>
> An argument for requiring
Robert Elz wrote, on 27 Sep 2019:
>
> | In the case of [x[:bogus:]], the use of both colons clearly indicates
> | the intention to use the new character-class feature. If the name
> | between the colons is not a valid class name, that is likely due to
> | an error on the user or
10 matches
Mail list logo