From: Kei Kebreau <kei@openmailbox.org>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: 02/06: gnu: Add python-openid.
Date: Mon, 10 Apr 2017 18:52:07 -0400 [thread overview]
Message-ID: <87r30z510o.fsf@openmailbox.org> (raw)
In-Reply-To: <87zifqggoy.fsf@netris.org> (Mark H. Weaver's message of "Sun, 09 Apr 2017 03:53:33 -0400")
[-- Attachment #1: Type: text/plain, Size: 777 bytes --]
Mark H Weaver <mhw@netris.org> writes:
> kei@openmailbox.org (Kei Kebreau) writes:
>
>> kkebreau pushed a commit to branch master
>> in repository guix.
>>
>> commit ccda56886625af84d34ebf1f26b22345e5dbe235
>> Author: ng0 <ng0@libertad.pw>
>> Date: Wed Feb 15 10:09:23 2017 +0000
>>
>> gnu: Add python-openid.
>>
>> * gnu/packages/python.scm (python-openid): New variable.
>>
>> Signed-off-by: Kei Kebreau <kei@openmailbox.org>
>
> We already have 'python-openid'. It's right above the one you just
> added. I reverted this commit.
>
> Please be more careful.
>
> Thanks,
> Mark
Aw, man. :-(
The really sad part is that I remember spotting this when I tested this
patch a few weeks ago. Your advice is noted.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-04-10 22:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170408164140.25323.26426@vcs0.savannah.gnu.org>
[not found] ` <20170408164141.90C48219E7@vcs0.savannah.gnu.org>
2017-04-09 7:53 ` 02/06: gnu: Add python-openid Mark H Weaver
2017-04-10 22:52 ` Kei Kebreau [this message]
[not found] ` <20170408164141.E7604219E7@vcs0.savannah.gnu.org>
2017-04-09 8:04 ` 04/06: gnu: Add python-django-gravatar2 Mark H Weaver
2017-04-09 8:20 ` Julien Lepiller
2017-04-09 9:15 ` ng0
2017-04-09 14:23 ` Julien Lepiller
2017-04-11 2:17 ` Kei Kebreau
[not found] ` <20170408164141.BC255219E7@vcs0.savannah.gnu.org>
2017-04-09 8:15 ` 03/06: gnu: Add python-django-allauth Mark H Weaver
2017-04-09 9:17 ` ng0
2017-04-10 22:46 ` Kei Kebreau
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r30z510o.fsf@openmailbox.org \
--to=kei@openmailbox.org \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).