all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Christopher Baines <mail@cbaines.net>
Cc: "Artyom V. Poptsov" <poptsov.artyom@gmail.com>, 67570@debbugs.gnu.org
Subject: [bug#67570] [PATCH] gnu: go-golang-org-x-sys: Update to 0.8.0.
Date: Mon, 08 Jan 2024 18:02:43 +0100	[thread overview]
Message-ID: <87eder4v2k.fsf@gnu.org> (raw)
In-Reply-To: <87cyudqhnq.fsf@cbaines.net> (Christopher Baines's message of "Sun, 07 Jan 2024 15:34:36 +0000")

Hi Chris!

Christopher Baines <mail@cbaines.net> skribis:

> Looks like these patches were sent long enough ago that they've dropped
> out of the fixed number of recent patches that QA looks at [1].

Would it be possible to keep previous build results beyond that number,
only marking them as “archived” or similar?  (And then after a longer
period of time, they can be removed altogether.)

It would allow us to get useful info even for old patches.

Thanks,
Ludo’.




  reply	other threads:[~2024-01-08 17:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-01 19:08 [bug#67570] [PATCH] gnu: kubo: Fix build Artyom V. Poptsov
2023-12-02 10:04 ` Ludovic Courtès
2023-12-09  8:22   ` [bug#67570] [PATCH] gnu: go-golang-org-x-sys: Update to 0.8.0. (was: [PATCH] gnu: kubo: Fix build.) Artyom V. Poptsov
2023-12-10 21:22     ` [bug#67570] [PATCH] gnu: go-golang-org-x-sys: Update to 0.8.0 Ludovic Courtès
2023-12-29  9:55       ` Artyom V. Poptsov
2024-01-07 14:48         ` bug#67570: " Ludovic Courtès
2024-01-07 15:34           ` [bug#67570] " Christopher Baines
2024-01-08 17:02             ` Ludovic Courtès [this message]
2024-01-08 17:13           ` Artyom V. Poptsov

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=87eder4v2k.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=67570@debbugs.gnu.org \
    --cc=mail@cbaines.net \
    --cc=poptsov.artyom@gmail.com \
    /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.