From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: pinoaffe@airmail.cc, 39514@debbugs.gnu.org
Subject: [bug#39514] [PATCH] update radare2 and cutter versions
Date: Sat, 15 Feb 2020 13:38:15 +0100 [thread overview]
Message-ID: <87blq0gh54.fsf@nckx> (raw)
In-Reply-To: <f70aaac9daabf248f299992ac10ee55d@airmail.cc>
[-- Attachment #1: Type: text/plain, Size: 1384 bytes --]
Pinoaffe,
pinoaffe@airmail.cc 写道:
> update radare2 and cutter, they need to be updated at the same
> time
> since old cutter doesn't build with new radare2 and new cutter
> doesn't
> build with old radare2
This is a good reason not to separate the two, although I'm unsure
what the commit message would look like.
> - (version "3.5.1")
> + (version "4.2.1")
Confusingly, their ‘releases’ page[0] lists 4.2.0 as ‘Latest
release’. As GitHub actively encourages poor release management
this might just be an oversight, but it would be nice if this were
clarified. Is 4.2.1 generally accepted as the current stable
release?
> + (file-name (string-append name "-" version
> "-checkout"))
There's a (git-file-name name version) helper that will do the
same thing, prettier.
> (description
> - "Radare project started as a forensics tool, a scriptable
> commandline
> + "Radare project started as a forensics tool, a scriptable
I'm going to improve the radare2 description on master so this
hunk can be dropped.
Would you be willing to send a V2 patch to this bug number (and
think of a good commit message following our standards[1])?
Kind regards,
T G-R
[0]: https://github.com/radareorg/radare2/releasesu
[1]: https://guix.gnu.org/manual/en/guix.html#Submitting-Patches
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2020-02-15 12:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-08 15:53 [bug#39514] [PATCH] update radare2 and cutter versions pinoaffe
2020-02-15 12:38 ` Tobias Geerinckx-Rice via Guix-patches via [this message]
2020-03-28 23:14 ` bug#39514: Done: " Jakub Kądziołka
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=87blq0gh54.fsf@nckx \
--to=guix-patches@gnu.org \
--cc=39514@debbugs.gnu.org \
--cc=me@tobias.gr \
--cc=pinoaffe@airmail.cc \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.