From: ifreund <ifreund@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: xdg-desktop-portal-wlr-0.2.0
Date: Thu, 18 Feb 2021 10:27:37 +0100 [thread overview]
Message-ID: <20210218092737.FoWlWmsM0C54emSJBzI72TVj-P6_SH6zz2OXU6JtUn4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28829@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1070 bytes --]
New comment by ifreund on void-packages repository
https://github.com/void-linux/void-packages/pull/28829#issuecomment-781207824
Comment:
@ericonr
```
10:21 <ifreund> emersion: what's the reasoning for xdg-desktop-portal-wlr being a pre-release? void doesn't usually accept projects marked as such into the repos: https://github.com/void-linux/void-packages/pull/28829#issuecomment-781047601
10:22 <ifreund> which is is a shame, because both chrome and firefox in the void repos are built with pipewire support now :)
10:23 <emersion> ifreund: i don't really understand. meson has version 0.57.0, is it in the repos?
10:23 <ifreund> xdpw 0.2.0 is listed as a pre-release by github here: https://github.com/emersion/xdg-desktop-portal-wlr/releases
10:24 <emersion> oh, the github thing? it's just something automatically done by my release script
10:25 <ifreund> does the script wait for 1.0 before marking it as a release? :D
10:25 <emersion> yea
10:25 <emersion> probably doesn't make a lot of sense
```
Edit: 0.2.0 is no longer marked as a pre-release :)
next prev parent reply other threads:[~2021-02-18 9:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-17 19:35 [PR PATCH] " ifreund
2021-02-17 22:48 ` paper42
2021-02-18 4:48 ` ericonr
2021-02-18 9:26 ` ifreund
2021-02-18 9:27 ` ifreund [this message]
2021-02-18 12:35 ` [PR PATCH] [Merged]: " ericonr
2021-02-18 15:29 ` st3r4g
2021-02-18 15:46 ` ericonr
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=20210218092737.FoWlWmsM0C54emSJBzI72TVj-P6_SH6zz2OXU6JtUn4@z \
--to=ifreund@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).