[debbugs-tracker] bug#28276: closed (pybitmessage: Update to 0.6.2)

[GNU bug Tracking System]

Your message dated Sat, 30 Sep 2017 15:26:33 +0100
with message-id <address@hidden>
and subject line Re: [bug#28276] pybitmessage: Update to 0.6.2
has caused the debbugs.gnu.org bug report #28276,
regarding pybitmessage: Update to 0.6.2
to be marked as done.

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


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

--- Begin Message --- Subject: pybitmessage: Update to 0.6.2 Date: Tue, 29 Aug 2017 12:38:58 +0000

The ticket will get the patch for the 0.6.1 -> 0.6.2 Update
today. I'm done, I just need to attend some other business
right now.
If you see the ticket now, check again in 1 - 3 hours.
-- 
ng0
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://n0is.noblogs.org/my-keys
https://www.infotropique.org https://krosos.org

signature.asc
Description: PGP signature

--- End Message ---

--- Begin Message --- Subject: Re: [bug#28276] pybitmessage: Update to 0.6.2 Date: Sat, 30 Sep 2017 15:26:33 +0100

On Sat, 30 Sep 2017 14:18:38 +0000
ng0 <address@hidden> wrote:

> Christopher Baines transcribed 1.5K bytes:
> > On Tue, 29 Aug 2017 14:06:04 +0000
> > ng0 <address@hidden> wrote:
> >   
> > > Last version of patch.  
> > 
> > I've had a look at the patch attached, and it looks ok to me (I've
> > never used pybitmessage). If you can confirm that this is definitely
> > good to be merged, I'm happy to merge it?  
> 
> I don't use Bitmessage anymore, but
> I have used this patch to send some messages around.

That sounds ok to me. I've now merged this patch :)

pgpy2Owfwnwre.pgp
Description: OpenPGP digital signature

--- End Message ---