etc/teams.scm regexp

  • Done
  • quality assurance status badge
Details
3 participants
  • Greg Hogan
  • Maxim Cournoyer
  • Simon Tournier
Owner
unassigned
Submitted by
Greg Hogan
Severity
normal
G
G
Greg Hogan wrote on 10 Aug 2023 15:34
(address . bug-guix@gnu.org)
CA+3U0Znxg8QwjqJMB8-7QjB58JxkGp91Q8if-463NhjZgDuHpA@mail.gmail.com
Hi,

I am seeing unapplied "#<regexp ...>" in some team scopes when running
`./etc/teams.scm list-teams`.

Greg
S
S
Simon Tournier wrote on 23 Aug 2023 18:34
864jkp1zv2.fsf@gmail.com
Hi,

On Thu, 10 Aug 2023 at 09:34, Greg Hogan <code@greghogan.com> wrote:

Toggle quote (3 lines)
> I am seeing unapplied "#<regexp ...>" in some team scopes when running
> `./etc/teams.scm list-teams`.


I do not know what it had never been merged. Probably because the
revamp for a v3 was more work than I could put in.

Cheers,
simon
M
M
Maxim Cournoyer wrote on 29 Aug 2023 21:22
(name . Simon Tournier)(address . zimon.toutoune@gmail.com)
87zg29ac1u.fsf@gmail.com
Hi,

Simon Tournier <zimon.toutoune@gmail.com> writes:

Toggle quote (12 lines)
> Hi,
>
> On Thu, 10 Aug 2023 at 09:34, Greg Hogan <code@greghogan.com> wrote:
>
>> I am seeing unapplied "#<regexp ...>" in some team scopes when running
>> `./etc/teams.scm list-teams`.
>
> This is done by <https://issues.guix.gnu.org/58660#17>.
>
> I do not know what it had never been merged. Probably because the
> revamp for a v3 was more work than I could put in.

Now installed!

Closing. Thanks for the report and for Simon for fixing it.

--
Thanks,
Maxim
Closed
S
S
Simon Tournier wrote on 5 Sep 2023 19:37
(name . Maxim Cournoyer)(address . maxim.cournoyer@gmail.com)
86sf7sr073.fsf@gmail.com
Hi Maxim,

On Tue, 29 Aug 2023 at 15:22, Maxim Cournoyer <maxim.cournoyer@gmail.com> wrote:

Toggle quote (2 lines)
> Closing. Thanks for the report and for Simon for fixing it.

Cool, thank you for the improvements.

Cheers,
simon
Closed
?
Your comment

This issue is archived.

To comment on this conversation send an email to 65208@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 65208
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch