From: "Ludovic Courtès" <ludo@gnu.org>
To: Christopher Baines <mail@cbaines.net>
Cc: guix-devel@gnu.org
Subject: Re: Progress with automating testing of patches
Date: Sat, 01 Oct 2022 18:34:05 +0200 [thread overview]
Message-ID: <878rlzec5e.fsf@gnu.org> (raw)
In-Reply-To: <87sfkneqmm.fsf@cbaines.net> (Christopher Baines's message of "Mon, 19 Sep 2022 09:46:51 +0200")
Hello!
As discussed in Paris, I’m a big fan of qa.guix.gnu.org! I like that it
shows all the information relevant to packagers and reviewers in a
concise way.
I wonder if it’s due to recent changes since I last looked, but I’m a
bit confused by the numbers in this example:
https://qa.guix.gnu.org/issue/58186
The numbers before/after patches don’t match and the lint warnings (nice
addition!) appear to unrelated to the patch at hand.
Any idea what’s going on?
Conversely, <https://qa.guix.gnu.org/issue/58072> looks fine, for
example.
BTW, Emacs users, I have this key binding that I find useful:
--8<---------------cut here---------------start------------->8---
(defun ludo-jump-to-guix-qa-url ()
"Jump to the QA page of the Debbugs issue at point."
(interactive)
(let ((url (concat "https://qa.guix.gnu.org/issue/"
(number-to-string (debbugs-gnu-current-id)))))
(browse-url url)))
(define-key debbugs-gnu-mode-map (kbd "C-M-j") 'ludo-jump-to-guix-qa-url)
--8<---------------cut here---------------end--------------->8---
Thanks!
Ludo’.
next prev parent reply other threads:[~2022-10-01 17:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 10:11 Progress with automating testing of patches Christopher Baines
2022-09-19 7:46 ` Christopher Baines
2022-10-01 16:34 ` Ludovic Courtès [this message]
2022-10-01 21:58 ` Christopher Baines
2022-10-05 10:01 ` Ludovic Courtès
2022-10-05 10:22 ` Christopher Baines
2022-10-06 13:31 ` Ludovic Courtès
2022-10-05 22:49 ` jbranso
2022-10-06 9:11 ` debbugs-guix.el helper function zimoun
2022-10-07 9:47 ` Ludovic Courtès
2022-11-15 15:09 ` zimoun
2022-10-06 13:32 ` Progress with automating testing of patches Ludovic Courtès
2022-10-06 15:22 ` Joshua Branson
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=878rlzec5e.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=mail@cbaines.net \
/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.