From: rivanfebrian123 <rivanfebrian123@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Inconsistent Firefox binary naming
Date: Thu, 31 Mar 2022 09:47:39 +0200 [thread overview]
Message-ID: <20220331074739.jFNt4SHm2RWyDCbMsIP-NdMXCsI7OVC3NECusJBEMqA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36404@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 257 bytes --]
New comment by rivanfebrian123 on void-packages repository
https://github.com/void-linux/void-packages/issues/36404#issuecomment-1084218397
Comment:
@Duncaen sorry, haven't check that.
I guess we need some patches. Another dirty fix with `sed`, maybe?
next prev parent reply other threads:[~2022-03-31 7:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 10:36 [ISSUE] " rivanfebrian123
2022-03-29 15:20 ` Duncaen
2022-03-29 17:34 ` wael444
2022-03-30 8:55 ` paper42
2022-03-31 7:47 ` rivanfebrian123 [this message]
2022-03-31 12:42 ` wael444
2022-04-07 19:30 ` paper42
2022-04-07 19:30 ` [ISSUE] [CLOSED] " paper42
2022-04-07 19:30 ` paper42
2022-04-08 5:40 ` rivanfebrian123
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=20220331074739.jFNt4SHm2RWyDCbMsIP-NdMXCsI7OVC3NECusJBEMqA@z \
--to=rivanfebrian123@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).