Github messages for voidlinux
 help / color / mirror / Atom feed
From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: dracut: update to 059.20231027
Date: Sat, 28 Oct 2023 15:44:49 +0200	[thread overview]
Message-ID: <20231028134449.3sMWmrKTVFveP-GNW5POfQatukFzdKDmnSu6SpK14tU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46936@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1542 bytes --]

New comment by ahesford on void-packages repository

https://github.com/void-linux/void-packages/pull/46936#issuecomment-1783815511

Comment:
No, the policy applies to all packages and is described at the end of the [requirements section of our contributor guidelines](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements). There are rare exceptions, of course. In particular, the Intel video driver is legacy software that is not generally recommended for X11 (the mode-setting driver is the recommended approach for Intel hardware). We tolerate a deviation from policy in this case because the legacy driver may be required for functionality with certain older hardware and backporting critical patches only would become an excessive maintenance burden. In the case of Dracut, it seems we're looking at only a few key patches to maintain functionality.

This case is complicated by the fact that some people, including you, maintain write privileges with Dracut but lack the authority to tag releases that we would accept as package updates. If this problem continues indefinitely, we can investigate other alternatives for keeping Dracut up to date. In the meantime, I hope that you and your collaborators can find a way to restore full, active maintenance of the project repository.

We appreciate the work you do to advance the state of Dracut and the fact that you remain mindful of the needs of distributions that do not use systemd (and, more generally, do not use it in initramfs images).

  parent reply	other threads:[~2023-10-28 13:44 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-28  3:36 [PR PATCH] dracut: update to 059+git20231027 LaszloGombos
2023-10-28  3:38 ` classabbyamp
2023-10-28  3:38 ` classabbyamp
2023-10-28  3:45 ` [PR PATCH] [Updated] " LaszloGombos
2023-10-28  3:45 ` LaszloGombos
2023-10-28  3:49 ` [PR PATCH] [Updated] dracut: update to 059.20231027 LaszloGombos
2023-10-28  3:55 ` LaszloGombos
2023-10-28  3:58 ` LaszloGombos
2023-10-28  3:59 ` [PR PATCH] [Updated] " LaszloGombos
2023-10-28 11:33 ` ahesford
2023-10-28 11:33 ` [PR PATCH] [Closed]: " ahesford
2023-10-28 12:08 ` LaszloGombos
2023-10-28 12:09 ` LaszloGombos
2023-10-28 13:43 ` ahesford
2023-10-28 13:44 ` ahesford
2023-10-28 13:44 ` ahesford [this message]
2023-10-28 13:51 ` zdykstra
2023-10-28 14:38 ` LaszloGombos
2023-10-28 14:51 ` zdykstra

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=20231028134449.3sMWmrKTVFveP-GNW5POfQatukFzdKDmnSu6SpK14tU@z \
    --to=ahesford@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).