all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Julian Flake <flake@uni-koblenz.de>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>,
	"Tobias Geerinckx-Rice" <me@tobias.gr>,
	"Julian Flake" <flake@uni-koblenz.de>,
	73428@debbugs.gnu.org
Subject: [bug#73428] update elogind to 255
Date: Wed, 02 Oct 2024 07:46:53 +0200	[thread overview]
Message-ID: <87ikubdpki.fsf@uni-koblenz.de> (raw)
In-Reply-To: <874j5vtjib.fsf@gmail.com> (Maxim Cournoyer's message of "Wed, 02 Oct 2024 09:51:08 +0900")

Hi Maxim,

On Wed, Oct 02 2024, Maxim Cournoyer wrote:

> I think QA won't currently attempt to build patch series that 
> would
> cause more than 1000 rebuilds.

thanks for the info. How can this patch be tested, then? Is there 
a lack of resources (metal)?

Best Regards,
Julian




      reply	other threads:[~2024-10-02  5:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-22 18:50 bug#73428: update elogind to 255 Julian Flake
2024-09-23 21:43 ` bug#73428: [PATCH] elogind update to 252.24 Julian Flake
2024-09-23 21:58   ` bug#73428: update elogind to 255 Julian Flake
2024-09-24  8:59     ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2024-09-24  9:02       ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2024-09-24 10:34         ` Julian Flake
2024-09-24 19:29           ` Julian Flake
2024-09-24  5:18 ` bug#73428: [PATCH v2 0/2] removed reference to deleted patch Julian Flake
2024-09-24  5:18   ` bug#73428: [PATCH v2 1/2] gnu: elogind update to 252.24 Julian Flake
2024-09-24  5:18   ` bug#73428: [PATCH v2 2/2] gnu: elogind: Remove unneeded rpath patch Julian Flake
2024-09-24  5:37     ` bug#73428: update elogind to 255 Julian Flake
     [not found] ` <87bk045089.fsf@gnu.org>
2024-09-30 21:08   ` [bug#73428] " Julian Flake
2024-10-02  0:51     ` Maxim Cournoyer
2024-10-02  5:46       ` Julian Flake [this message]

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=87ikubdpki.fsf@uni-koblenz.de \
    --to=flake@uni-koblenz.de \
    --cc=73428@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    --cc=me@tobias.gr \
    /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.