all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Vivien Kraus via Guix-patches via <guix-patches@gnu.org>
To: control@debbugs.gnu.org, 68937@debbugs.gnu.org
Subject: [bug#68937] QA review for 68937
Date: Sat, 10 Feb 2024 09:12:38 +0100	[thread overview]
Message-ID: <14bda2dd47fc43c425538d529f298a000d405f4e.camel@planete-kraus.eu> (raw)
In-Reply-To: <cover.1707146219.git.dariqq@posteo.net>

user guix
usertag 68937 + reviewed-looks-good
thanks

Guix QA review form submission:
The new lint warning is Guix’ fault I think.

I checked orca and it still reads the screen correctly. I’m not a
regular user of orca.

I’m not a maintainer, I’m not a committer. I’m a relatively new member
of the GNOME team.

I’ve been involved as I asked for the patches to be rebased on gnome-
team.

Items marked as checked: Package builds, Commit messages





  parent reply	other threads:[~2024-02-10  8:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-05 15:44 [bug#68937] [PATCH 0/3] Orca fixes Dariqq
2024-02-05 15:48 ` [bug#68937] [PATCH 1/3] gnu: orca: Fix invocation errors Dariqq
2024-02-05 15:48 ` [bug#68937] [PATCH 2/3] gnu: brltty: Fix python package install Dariqq
2024-02-05 15:48 ` [bug#68937] [PATCH 3/3] gnu: orca: Add more optional dependencies Dariqq
2024-02-05 16:50 ` [bug#68937] [PATCH 0/3] Orca fixes Vivien Kraus via Guix-patches via
2024-02-05 18:32   ` Dariqq
2024-02-05 18:49 ` [bug#68937] [PATCH gnome-team v2 1/2] gnu: brltty: Fix python package install Dariqq
2024-02-05 18:49   ` [bug#68937] [PATCH gnome-team v2 2/2] gnu: orca: Add optional dependencies Dariqq
2024-02-16 19:49     ` Maxim Cournoyer
2024-02-10  8:12 ` Vivien Kraus via Guix-patches via [this message]
2024-02-10 11:11   ` [bug#68937] QA review for 68937 Christopher Baines
2024-02-10 11:15     ` bug#68937: " Christopher Baines

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=14bda2dd47fc43c425538d529f298a000d405f4e.camel@planete-kraus.eu \
    --to=guix-patches@gnu.org \
    --cc=68937@debbugs.gnu.org \
    --cc=control@debbugs.gnu.org \
    --cc=vivien@planete-kraus.eu \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.