From: Andreas Enge <andreas@enge.fr>
To: Josselin Poiret <dev@jpoiret.xyz>
Cc: guix-devel@gnu.org
Subject: Re: Gnome dans core-updates
Date: Sun, 19 Mar 2023 10:59:56 +0100 [thread overview]
Message-ID: <ZBbdHNSxO7G4s3rE@jurong> (raw)
In-Reply-To: <87cz55rtb8.fsf@jpoiret.xyz>
Am Sun, Mar 19, 2023 at 10:20:27AM +0100 schrieb Josselin Poiret:
> The project does seem functional, they just seem to not care about
> making new releases, since they direct users to official builds of HEAD
> [1]. Maybe we could just point there as well?
> [1] https://github.com/ipxe/ipxe/discussions/679
Well, I am loath to this attitude "just take the latest master", and it is
not what we normally do. A software writer cannot expect distros (nor end
users, as they seem to prefer) to follow each and every of their commits.
And it does not reflect well on their quality assurance processes if they
are unable to single out a commit from time to time that has undergone more
thorough scrutiny.
That said, if just backporting one fix does not solve the problem, we may
have to go this route...
Andreas
next prev parent reply other threads:[~2023-03-19 10:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 19:40 Gnome dans core-updates Andreas Enge
2023-03-17 19:45 ` Andreas Enge
2023-03-17 20:46 ` Liliana Marie Prikler
2023-03-17 20:58 ` Liliana Marie Prikler
2023-03-18 9:53 ` Andreas Enge
2023-03-17 23:00 ` Liliana Marie Prikler
2023-03-18 10:36 ` Andreas Enge
2023-03-18 11:15 ` Liliana Marie Prikler
2023-03-18 17:57 ` Andreas Enge
2023-03-18 10:07 ` Andreas Enge
2023-03-18 10:18 ` Andreas Enge
2023-03-19 9:20 ` Josselin Poiret
2023-03-19 9:59 ` Andreas Enge [this message]
2023-03-19 14:14 ` Josselin Poiret
2023-03-20 17:00 ` Andreas Enge
2023-03-20 17:11 ` Andreas Enge
2023-03-20 17:17 ` Efraim Flashner
2023-03-20 17:52 ` Andreas Enge
2023-03-20 19:18 ` Josselin Poiret
2023-03-30 9:08 ` Andreas Enge
2023-04-05 8:54 ` Andreas Enge
2023-04-07 13:45 ` Andreas Enge
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=ZBbdHNSxO7G4s3rE@jurong \
--to=andreas@enge.fr \
--cc=dev@jpoiret.xyz \
--cc=guix-devel@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).