From: Leo Famulari <leo@famulari.name>
To: guix-devel@gnu.org
Subject: Re: [PATCH 0/5] Install docs for Let's Encrypt
Date: Sat, 20 Feb 2016 02:48:44 -0500 [thread overview]
Message-ID: <20160220074844.GA16805@jasmine> (raw)
In-Reply-To: <cover.1455767577.git.leo@famulari.name>
On Wed, Feb 17, 2016 at 10:53:48PM -0500, Leo Famulari wrote:
> These patches add what's needed to build info files and manpages for
> letsencrypt and python-acme.
>
> I'd appreciate some feedback on the 'docs' phases added to letsencrypt
> and python-acme. Specifically, is my use of (and) correct?
If there are no more comments, I'll incorporate my reviewers' helpful
comments and push in the next day or so.
>
> Leo Famulari (5):
> gnu: Add python-sphinxcontrib-programoutput.
> licenses: Add repoze license.
> gnu: Add python-sphinx-repoze-autointerface.
> gnu: letsencrypt: Generate and install documentation.
> gnu: python-acme: Generate and install documentation.
>
> gnu/packages/python.scm | 54 ++++++++++++++++++++++++++++++++++++++++++++++++-
> gnu/packages/tls.scm | 47 ++++++++++++++++++++++++++++++++++++------
> guix/licenses.scm | 7 +++++++
> 3 files changed, 101 insertions(+), 7 deletions(-)
>
> --
> 2.6.3
>
prev parent reply other threads:[~2016-02-20 7:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 3:53 [PATCH 0/5] Install docs for Let's Encrypt Leo Famulari
2016-02-18 3:53 ` [PATCH 1/5] gnu: Add python-sphinxcontrib-programoutput Leo Famulari
2016-02-18 3:53 ` [PATCH 2/5] licenses: Add repoze license Leo Famulari
2016-02-18 3:53 ` [PATCH 3/5] gnu: Add python-sphinx-repoze-autointerface Leo Famulari
2016-02-18 8:28 ` Alex Kost
2016-02-18 17:40 ` Leo Famulari
2016-02-18 3:53 ` [PATCH 4/5] gnu: letsencrypt: Generate and install documentation Leo Famulari
2016-02-18 3:53 ` [PATCH 5/5] gnu: python-acme: " Leo Famulari
2016-02-18 12:51 ` Ricardo Wurmus
2016-02-18 17:46 ` Leo Famulari
2016-02-18 19:36 ` Andreas Enge
2016-02-20 7:48 ` Leo Famulari [this message]
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=20160220074844.GA16805@jasmine \
--to=leo@famulari.name \
--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).