bug#39830: closed ([PATCH] gnu: python-binwalk: Update to 2.2.0)

[GNU bug Tracking System]

Your message dated Sun, 1 Mar 2020 14:12:32 +0100
with message-id <20200301131232.clmpfoomu6vbp24e@gravity>
and subject line Re: [PATCH] gnu: python-binwalk: Update to 2.2.0
has caused the debbugs.gnu.org bug report #39830,
regarding [PATCH] gnu: python-binwalk: Update to 2.2.0
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden.)


-- 
39830: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=39830
GNU Bug Tracking System
Contact address@hidden with problems

--- Begin Message --- Subject: [PATCH] gnu: python-binwalk: Update to 2.2.0 Date: Sat, 29 Feb 2020 01:22:49 +0100

Tested by running it on a sample of /lib/firmware/* from another linux
distribution, it found a bunch of binary thingies in there...

-- 
Vincent Legoll

0001-gnu-python-xyz-Update-to-2.2.0.patch
Description: Text Data

--- End Message ---

--- Begin Message --- Subject: Re: [PATCH] gnu: python-binwalk: Update to 2.2.0 Date: Sun, 1 Mar 2020 14:12:32 +0100

On Sat, Feb 29, 2020 at 01:22:49AM +0100, Vincent Legoll wrote:
> Tested by running it on a sample of /lib/firmware/* from another linux
> distribution, it found a bunch of binary thingies in there...
Thanks! The commit we were using before was just one behind the release
tag, so it's not really an update. Also, it's not necessary to use a
commit hash when there is a tagged release. See commit
9b9ab657cc9df579cdb2ff9282a7117a86212d31, which I based upon your patch.

signature.asc
Description: PGP signature

--- End Message ---