unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 0/6] Pytest update
Date: Mon, 11 Jul 2016 10:29:48 +0200	[thread overview]
Message-ID: <87furgo9vn.fsf@gnu.org> (raw)
In-Reply-To: <20160703201517.GA26140@jasmine> (Leo Famulari's message of "Sun, 3 Jul 2016 16:15:17 -0400")

Leo Famulari <leo@famulari.name> skribis:

> On Sun, Jul 03, 2016 at 08:58:39AM +0300, Efraim Flashner wrote:
>> The patch-set looks good to me. For the curious, I checked python-pytest
>> and python2-pytest and ended up with 81 packages and 235 dependants, but
>> some of those are from my WIP tree in GUIX_PACKAGE_PATH
>
> What branch should it go on?
>
> Also, it would be good to push this series and the Sphinx series
> together.
>
> $ guix refresh -l python-sphinx python2-sphinx python-pytest python2-pytest
> Building the following 84 packages would ensure 229 dependent packages are rebuilt:
> [...]
>
> So, it's basically the same set of packages that would need to be
> re-built.

The ‘python-updates’ branch would seem right to me.

Thanks,
Ludo’.

  parent reply	other threads:[~2016-07-11  8:29 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-03  1:10 [PATCH 0/6] Pytest update Leo Famulari
2016-07-03  1:10 ` [PATCH 1/6] gnu: python-virtualenv: Disable tests Leo Famulari
2016-07-03  1:10 ` [PATCH 2/6] gnu: python-pip: " Leo Famulari
2016-07-03  1:10 ` [PATCH 3/6] gnu: python-scripttest: " Leo Famulari
2016-07-03  1:10 ` [PATCH 4/6] gnu: python-pytest: Update to 2.9.2 Leo Famulari
2016-07-03  1:10 ` [PATCH 5/6] gnu: python-pytest-runner: Update to 2.8 Leo Famulari
2016-07-03  1:10 ` [PATCH 6/6] gnu: python-cryptopgraphy: Update to 1.4 Leo Famulari
2016-07-03  5:58 ` [PATCH 0/6] Pytest update Efraim Flashner
2016-07-03 20:15   ` Leo Famulari
2016-07-07  1:13     ` Leo Famulari
2016-07-11  8:29     ` Ludovic Courtès [this message]
2016-07-11 15:50       ` Leo Famulari
2016-07-11 16:05         ` Leo Famulari
2016-07-12  9:14         ` python-updates! Ludovic Courtès
2016-07-16 21:23           ` python-updates! Christopher Allan Webber
2016-08-04 20:56         ` python-updates Ludovic Courtès
2016-08-04 21:23           ` python-updates Leo Famulari
2016-08-04 21:54             ` python-updates Leo Famulari
2016-08-05 12:13               ` python-updates Andreas Enge
2016-08-05 15:06                 ` python-updates Leo Famulari
2016-08-05 15:43                   ` python-updates Leo Famulari
2016-08-05 21:42                   ` python-updates Andreas Enge
2016-08-05 21:57                     ` python-updates Mark H Weaver
2016-08-05 23:03                       ` python-updates Leo Famulari

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=87furgo9vn.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    /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).