From: Frederick Muriithi <fredmanglis@gmail.com>
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 2/4] gnu: Add python-sphinx-1.5.2, python-sphinx-1.5.3
Date: Sun, 26 Mar 2017 18:32:49 +0300 [thread overview]
Message-ID: <CALjrZwbMCdH=QvLiBoXz1J1SCfQdDiO87zf7GQhW2huxvSkS1A@mail.gmail.com> (raw)
In-Reply-To: <20170326151058.GB13943@monza>
On Sun, Mar 26, 2017 at 6:10 PM, Pjotr Prins <pjotr.public12@thebird.nl> wrote:
> Hi Fred,
>
> Why do we need both versions?
>
We don't. I noticed there was a newer version (1.5.3) while working on
version 1.5.2, and thought to just add it, since it wasn't much
effort.
If it's ever explicitly needed, it'll be defined already. Is that
okay, or should I refrain from that in the future?
next prev parent reply other threads:[~2017-03-26 15:33 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-26 9:23 [PATCH 1/4] gnu: Add python-pytest-3.0.7 Muriithi Frederick Muriuki
2017-03-26 9:23 ` [PATCH 2/4] gnu: Add python-sphinx-1.5.2, python-sphinx-1.5.3 Muriithi Frederick Muriuki
2017-03-26 15:10 ` Pjotr Prins
2017-03-26 15:32 ` Frederick Muriithi [this message]
2017-03-26 16:40 ` Pjotr Prins
2017-03-27 19:10 ` Ricardo Wurmus
2017-03-27 15:11 ` Leo Famulari
2017-03-27 15:12 ` Leo Famulari
2017-03-28 20:03 ` Leo Famulari
2017-03-26 9:23 ` [PATCH 3/4] gnu: Add python-paramunittest Muriithi Frederick Muriuki
2017-03-26 15:12 ` Pjotr Prins
2017-03-26 15:47 ` Frederick Muriithi
2017-03-26 23:32 ` Chris Marusich
2017-03-27 2:41 ` Frederick Muriithi
2017-03-28 5:16 ` Frederick Muriithi
2017-03-28 19:25 ` Ludovic Courtès
2017-03-28 20:03 ` Leo Famulari
2017-03-26 9:23 ` [PATCH 4/4] gnu: Add python-mando Muriithi Frederick Muriuki
2017-03-26 15:16 ` Pjotr Prins
2017-03-27 15:14 ` Leo Famulari
2017-03-28 19:28 ` Ludovic Courtès
2017-03-28 20:04 ` Leo Famulari
2017-03-26 15:10 ` [PATCH 1/4] gnu: Add python-pytest-3.0.7 Pjotr Prins
[not found] ` <CALjrZwaRUvrctcwwFQ_5isqwoaaEq=77P2qFHwk1FL2mJ5T-dg@mail.gmail.com>
[not found] ` <CALjrZwaah9_Vv+MVTm2aiA_-WHycYhn=KCnk5KjsXo=8z0+QDA@mail.gmail.com>
2017-03-26 15:29 ` Frederick Muriithi
2017-03-27 15:09 ` Leo Famulari
2017-03-28 20:05 ` Leo Famulari
2017-03-28 20:04 ` 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='CALjrZwbMCdH=QvLiBoXz1J1SCfQdDiO87zf7GQhW2huxvSkS1A@mail.gmail.com' \
--to=fredmanglis@gmail.com \
--cc=guix-devel@gnu.org \
--cc=pjotr.public12@thebird.nl \
/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).