From: Marius Bakke <mbakke@fastmail.com>
To: Danny Milosavljevic <dannym@scratchpost.org>, guix-devel@gnu.org
Subject: Re: [PATCH 1/1] gnu: python-matplotlib: Fix documentation reST markup error.
Date: Thu, 05 Jan 2017 15:55:58 +0100 [thread overview]
Message-ID: <878tqpy2rl.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <20170104212220.20969-2-dannym@scratchpost.org>
[-- Attachment #1: Type: text/plain, Size: 1043 bytes --]
Danny Milosavljevic <dannym@scratchpost.org> writes:
> * gnu/packages/python.scm (python-matplotlib): Fix documentation reST markup error.
> ---
> gnu/packages/python.scm | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/gnu/packages/python.scm b/gnu/packages/python.scm
> index 4e1a6b4a8..bc9058ba3 100644
> --- a/gnu/packages/python.scm
> +++ b/gnu/packages/python.scm
> @@ -3629,6 +3629,11 @@ transcendental functions).")
> (sha256
> (base32
> "1dn05cvd0g984lzhh72wa0z93psgwshbbg93fkab6slx5m3l95av"))
> + (modules '((guix build utils)))
> + (snippet
> + '(substitute* "doc/users/intro.rst"
> + ;; Fix reST markup error (see <https://github.com/sphinx-doc/sphinx/issues/3044>)
> + (("[[][*][]]") "[#]")))
Please run this substitution in a phase instead. Source snippets change
the source presented to users running `guix build -S` and should be
reserved for critical bug fixes and reproducibility problems, but
otherwise stay as close to upstream as possible.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
prev parent reply other threads:[~2017-01-05 14:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 21:22 [PATCH 0/1] Fix reST markup error in matplotlib documentation, Danny Milosavljevic
2017-01-04 21:22 ` [PATCH 1/1] gnu: python-matplotlib: Fix documentation reST markup error Danny Milosavljevic
2017-01-05 14:55 ` Marius Bakke [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878tqpy2rl.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me \
--to=mbakke@fastmail.com \
--cc=dannym@scratchpost.org \
--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 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.