GNU bug report logs - #25808
Updating alot (and other collateral updates)

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Ricardo Wurmus <rekado <at> elephly.net>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#25808: closed (Updating alot (and other collateral updates))
Date: Tue, 10 Oct 2017 21:13:02 +0000

[Message part 1 (text/plain, inline)]

Your message dated Tue, 10 Oct 2017 23:11:19 +0200
with message-id <87wp42lnd4.fsf <at> elephly.net>
and subject line Re: bug#25808: Updating alot (and other collateral updates)
has caused the debbugs.gnu.org bug report #25808,
regarding Updating alot (and other collateral updates)
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
25808: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=25808
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Troy Sankey <sankeytms <at> gmail.com>
To: guix-patches <at> gnu.org
Subject: Updating alot (and other collateral updates)
Date: Mon, 20 Feb 2017 01:37:34 -0500

My ultimate goal with this patch set was to update alot and all of its
(python) dependency closure.

[PATCH 1/8] gnu: Add python-attrs.
[PATCH 2/8] gnu: Add python-constantly.
[PATCH 3/8] gnu: Add python-m2r.
[PATCH 4/8] gnu: python-setuptools-scm: Update to 1.15.0.
[PATCH 5/8] gnu: Add python-automat.
[PATCH 6/8] gnu: Add python-incremental.
[PATCH 7/8] gnu: python-twisted: Update to 17.1.0.
[PATCH 8/8] gnu: alot: Update to 0.5.1.

Troy

[Message part 3 (message/rfc822, inline)]

From: Ricardo Wurmus <rekado <at> elephly.net>
To: Troy Sankey <sankeytms <at> gmail.com>
Cc: 25808-done <at> debbugs.gnu.org
Subject: Re: bug#25808: Updating alot (and other collateral updates)
Date: Tue, 10 Oct 2017 23:11:19 +0200

Hi Troy,

Ricardo Wurmus <rekado <at> elephly.net> writes:

> Troy Sankey <sankeytms <at> gmail.com> writes:
>
>> Debbugs split off half of my patches in this series and created
>> individual bugs for them.  Sorry, I don't understand why.  I used
>> git send-email like I normally would on guix-devel <at> gnu.org.
>
> It’s best to send a single email (e.g. the cover letter) to
> guix-patches <at> gnu.org first, wait for confirmation from debbugs, and then
> send all the patches to the bug address (e.g. 25808 <at> debbugs.gnu.org).
>
> BTW: I see that these patches have not been pushed yet.  Do you plan on
> sending updated patches?


I have taken your patches, made the changes suggested by Marius, updated
some of the packages to the latest version and pushed them to master
with commit 3f81ca324.

Thanks again for your contribution!

-- 
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.