unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ng0 <ng0@libertad.pw>
To: guix-devel@gnu.org
Subject: Re: New python build system merged
Date: Wed, 30 Nov 2016 13:58:02 +0000	[thread overview]
Message-ID: <87eg1thxxx.fsf@we.make.ritual.n0.is> (raw)
In-Reply-To: <87oa0xkucz.fsf@gnu.org>

Ludovic Courtès <ludo@gnu.org> writes:

> ng0 <ng0@libertad.pw> skribis:
>
>> Hartmut Goebel <h.goebel@crazy-compilers.com> writes:
>>
>>> Am 29.11.2016 um 15:27 schrieb Ludovic Courtès:
>>>> Good.  When you fix it (and other failures, if any), we can start a new
>>>> evaluation or merge directly in master (the sooner the better!).
>>>
>>> Done.
>>>
>>> I'm very glad the new python build system is now in master. Thanks to
>>> everybody who helped finishing this!
>>>
>>> -- 
>>> Regards
>>> Hartmut Goebel
>>>
>>> | Hartmut Goebel          | h.goebel@crazy-compilers.com               |
>>> | www.crazy-compilers.com | compilers which you thought are impossible |
>>
>> Great job!
>>
>> So should I fix up all my ~70 or how many there are python
>> packages which I've sent in since september to get someone (or
>> hopefully multiple someones) to review them?
>
> Please do ping people.  Most likely the patch series fell into the
> cracks and only you can remind people of it.

Most likely, but there were also other issues. Like Harmut wanted
to do gunicorn while I was working on it at some point, so I
dropped that the series was forgotten. But I need to fix
conflicts anyway. I guess I can send in most of them by sunday,
there were also issues in many of the packages I need to
address. When I do this before people start to work on them it's
a bit easier to review as old issues aren't repeated.

I think most of them were in version-control, python,
networking, and it included the patches for kallithea, searx, and
some other software.

> I think Hartmut would be a good candidate to review them, Hartmut is our
> Python expert now.  :-)
>
> Ludo’.
>

-- 
♥Ⓐ  ng0  | ng0.chaosnet.org

  reply	other threads:[~2016-11-30 13:58 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-25 12:49 Please set up hdyra-job for python-branch Hartmut Goebel
2016-11-26  4:48 ` Leo Famulari
2016-11-28  9:21   ` Hartmut Goebel
2016-11-28 13:40     ` Ludovic Courtès
2016-11-29  9:54       ` Hartmut Goebel
2016-11-29 14:27         ` Ludovic Courtès
2016-11-29 18:09           ` New python build system merged Hartmut Goebel
2016-11-29 21:12             ` Leo Famulari
2016-11-30  8:20               ` Danny Milosavljevic
2016-11-30 15:02                 ` Hartmut Goebel
2016-11-30 16:59                   ` Leo Famulari
2016-11-30 17:26                     ` Leo Famulari
2016-11-30 17:30                       ` Leo Famulari
2016-12-01 14:10                         ` Ludovic Courtès
2016-11-30 17:30                     ` Hartmut Goebel
2016-11-30 20:41                       ` Leo Famulari
2016-12-01 14:13                         ` Hydra replacement and all that Ludovic Courtès
2016-11-30 10:41               ` New python build system merged Leo Famulari
2016-11-29 23:46             ` ng0
2016-11-30 12:47               ` Ludovic Courtès
2016-11-30 13:58                 ` ng0 [this message]
2016-11-30 12:40             ` Ludovic Courtès
2016-12-05 19:30             ` Leo Famulari
2016-12-06  9:22               ` Ludovic Courtès

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=87eg1thxxx.fsf@we.make.ritual.n0.is \
    --to=ng0@libertad.pw \
    --cc=guix-devel@gnu.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).