From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 0/6] Pytest update
Date: Mon, 11 Jul 2016 11:50:47 -0400 [thread overview]
Message-ID: <20160711155047.GA4630@jasmine> (raw)
In-Reply-To: <87furgo9vn.fsf@gnu.org>
On Mon, Jul 11, 2016 at 10:29:48AM +0200, Ludovic Courtès wrote:
> The ‘python-updates’ branch would seem right to me.
The brand new python-updates branch is now ready for more Python-related
commits!
next prev parent reply other threads:[~2016-07-11 15:51 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
2016-07-11 15:50 ` Leo Famulari [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160711155047.GA4630@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=ludo@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.