From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: [RFC] base-{minimal,voidstrap}: rename to base-container{,-full}
Date: Sat, 02 Dec 2023 00:15:54 +0100 [thread overview]
Message-ID: <20231201231554.pvytxxvX4aesAYudAjKZ07JOpSpuBWatOwdCycQtwxo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45565@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 585 bytes --]
There's a merged pull request on the void-packages repository
[RFC] base-{minimal,voidstrap}: rename to base-container{,-full}
https://github.com/void-linux/void-packages/pull/45565
Description:
If we don't want to do this, I'd be fine with just changing the description.
This makes it more clear that it's not meant for normal usage. Provide a transitional package because this could ruin someone's day.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **briefly**
[ci skip]
prev parent reply other threads:[~2023-12-01 23:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-12 17:24 [PR PATCH] [RFC] base-minimal: rename to base-container classabbyamp
2023-08-12 17:33 ` [PR PATCH] [Updated] " classabbyamp
2023-08-12 17:37 ` ahesford
2023-08-12 17:42 ` [PR PATCH] [Updated] " classabbyamp
2023-08-12 17:43 ` [PR PATCH] [Updated] [RFC] base-{minimal,voidstrap}: rename to base-container{,-full} classabbyamp
2023-08-12 17:46 ` classabbyamp
2023-08-12 17:48 ` classabbyamp
2023-08-14 11:56 ` Zapeth
2023-08-14 12:03 ` Zapeth
2023-08-14 12:03 ` Zapeth
2023-08-14 13:42 ` ahesford
2023-08-14 14:07 ` Zapeth
2023-11-13 1:46 ` github-actions
2023-11-30 15:13 ` [PR PATCH] [Updated] " classabbyamp
2023-12-01 23:15 ` classabbyamp [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=20231201231554.pvytxxvX4aesAYudAjKZ07JOpSpuBWatOwdCycQtwxo@z \
--to=classabbyamp@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).