From: abenson <abenson@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: i3: update to 4.22.
Date: Tue, 03 Jan 2023 17:23:21 +0100 [thread overview]
Message-ID: <20230103162321.SbiFdPsvtccfH6aL5V6Kwz5NLmgrK3SewEkRo2S1eh4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41418@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1107 bytes --]
New comment by abenson on void-packages repository
https://github.com/void-linux/void-packages/pull/41418#issuecomment-1369965867
Comment:
i3-gaps will be replaced with i3; basically i3-gaps becomes an empty shell
and pulls in i3.
i3-gaps is archived upstream already.
On Tue, Jan 3, 2023 at 9:44 AM Rodrigo Oliveira ***@***.***>
wrote:
> ***@***.**** commented on this pull request.
> ------------------------------
>
> In srcpkgs/i3/template
> <https://github.com/void-linux/void-packages/pull/41418#discussion_r1060709683>
> :
>
> > @@ -28,3 +28,9 @@ i3-devel_package() {
> vmove usr/include
> }
> }
> +
> +i3-gaps_package() {
>
> will this allow i3-gaps updates to this new release? or will just
> deprecate i3-gaps and install i3?
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/void-linux/void-packages/pull/41418#pullrequestreview-1234740946>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AABXP5N4VLHSVYE74SJPHX3WQRCPVANCNFSM6AAAAAATPIU2SA>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
next prev parent reply other threads:[~2023-01-03 16:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 3:11 [PR PATCH] " abenson
2023-01-03 15:44 ` [PR REVIEW] " mdkcore0
2023-01-03 16:23 ` abenson [this message]
2023-01-03 16:50 ` mdkcore0
2023-01-05 1:28 ` [PR PATCH] [Merged]: " abenson
2023-01-03 4:34 [PR PATCH] " mdkcore0
2023-01-03 5:57 ` paper42
2023-01-03 11:42 ` mdkcore0
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=20230103162321.SbiFdPsvtccfH6aL5V6Kwz5NLmgrK3SewEkRo2S1eh4@z \
--to=abenson@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).