Github messages for voidlinux
 help / color / mirror / Atom feed
From: Johnnynator <Johnnynator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: radare2: update to 5.4.2, new package: iaito
Date: Tue, 23 Nov 2021 23:13:35 +0100	[thread overview]
Message-ID: <20211123221335.ywk6emttVZL1F17mzpnbkOsBb29PTQOjjXsjl7cdcMQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33608@inbox.vuxu.org>

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

New comment by Johnnynator on void-packages repository

https://github.com/void-linux/void-packages/pull/33608#issuecomment-977217829

Comment:
https://github.com/void-linux/void-packages/pull/34221

> It should be really similar to the radare2 package since the fork is relatively recent and thus much of the codebase is actually the same.

At least for me auto analysis was extremely slow and unreliable in r2 with at least one case, rizin doesn't have the same problem. (also kinda the reason I never got much into using r2 for like anything).

Could you cleanup the PR to only include iaito as new package and the r2 update?

  parent reply	other threads:[~2021-11-23 22:13 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-17 19:32 [PR PATCH] " heittpr
2021-10-17 19:36 ` [PR PATCH] [Updated] " heittpr
2021-10-20  7:21 ` ericonr
2021-10-20 11:00 ` [PR PATCH] [Updated] " heittpr
2021-10-21 17:45 ` heittpr
2021-10-21 18:59 ` ericonr
2021-10-21 19:09 ` ericonr
2021-10-21 19:17 ` heittpr
2021-10-22 17:28 ` heittpr
2021-11-23 22:13 ` Johnnynator [this message]
2022-05-13 16:54 ` ericonr
2022-05-13 17:20 ` ypsvlq
2022-05-14  0:42 ` ericonr
2022-05-14  7:51 ` ypsvlq
2022-05-14  7:52 ` ypsvlq
2022-08-13  2:11 ` github-actions
2022-08-27  2:15 ` [PR PATCH] [Closed]: " github-actions

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=20211123221335.ywk6emttVZL1F17mzpnbkOsBb29PTQOjjXsjl7cdcMQ@z \
    --to=johnnynator@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).