unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: jbranso@dismail.de
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Progress with automating testing of patches
Date: Wed, 05 Oct 2022 22:49:22 +0000	[thread overview]
Message-ID: <20a86654f42bf996c4f3bacaa4ed89e9@dismail.de> (raw)
In-Reply-To: <878rlzec5e.fsf@gnu.org>

October 1, 2022 1:08 PM, "Ludovic Courtès" <ludo@gnu.org> wrote:

> 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---

Would it make sense to add something like this to debbugs?

I just created a debbugs-guix.el file in debbugs.  The update should be
available on elpa by now.

https://issues.guix.gnu.org/56987

> 
> Thanks!
> 
> Ludo’.


  parent reply	other threads:[~2022-10-05 22:49 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
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 [this message]
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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20a86654f42bf996c4f3bacaa4ed89e9@dismail.de \
    --to=jbranso@dismail.de \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).