Github messages for voidlinux
 help / color / mirror / Atom feed
From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: patchelf: update to 0.12.
Date: Wed, 02 Jun 2021 15:34:48 +0200	[thread overview]
Message-ID: <20210602133448.2nNkJd7Q8Kl7hvlxx5JoCDGPXLEEGH4w1hs5zSHfnfI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31104@inbox.vuxu.org>

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

New comment by sgn on void-packages repository

https://github.com/void-linux/void-packages/pull/31104#issuecomment-853032912

Comment:
On 2021-06-02 06:28:46-0700, Evgeny Ermakov ***@***.***> wrote:
> > Can it be created with autotools? 
> 
> Sure, but as I understand, @sgn is [against](https://github.com/void-linux/void-packages/pull/31104#issuecomment-849279446) this.

Well, I didn't know it includes a hash there.
Anyway, I advocated for another approach. I may make a proposal this
weekend.

-- 
Danh


  parent reply	other threads:[~2021-06-02 13:34 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-25  1:10 [PR PATCH] " unspecd
2021-05-27  2:57 ` sgn
2021-05-27  5:44 ` unspecd
2021-05-27  5:49 ` [PR PATCH] [Updated] " unspecd
2021-05-27  5:51 ` unspecd
2021-05-28 19:41 ` ahesford
2021-05-28 19:41 ` ahesford
2021-05-29  6:37 ` [PR PATCH] [Updated] " unspecd
2021-05-29  6:38 ` unspecd
2021-06-02 10:14 ` ahesford
2021-06-02 13:28 ` unspecd
2021-06-02 13:34 ` sgn [this message]
2021-06-16 12:29 ` ericonr
2021-06-16 12:29 ` sgn
2021-06-16 13:05 ` ahesford
2022-01-06  2:16 ` [PR PATCH] [Updated] " unspecd
2022-01-06  2:17 ` patchelf: update to 0.14.3 unspecd
2022-03-22  6:40 ` [PR PATCH] [Updated] " unspecd
2022-03-22  6:43 ` patchelf: update to 0.14.5 unspecd
2022-03-22 10:36 ` [PR PATCH] [Merged]: " ahesford
2021-06-16 10:17 [PR PATCH] patchelf: update to 0.12 ailiop-git
2021-06-16 12:29 ` 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=20210602133448.2nNkJd7Q8Kl7hvlxx5JoCDGPXLEEGH4w1hs5zSHfnfI@z \
    --to=sgn@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).