From: Pierre Neidhardt <mail@ambrevar.xyz>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: 16/16: doc: Discourage the use of texlive as input
Date: Sat, 15 Dec 2018 19:23:01 +0100 [thread overview]
Message-ID: <875zvusl8a.fsf@ambrevar.xyz> (raw)
In-Reply-To: <874lbey7v2.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 137 bytes --]
Done.
(Oops, missing period in the commit message... I guess I'm having a day off :p)
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
prev parent reply other threads:[~2018-12-15 18:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181214223246.22997.58804@vcs0.savannah.gnu.org>
[not found] ` <20181214223250.89D882118D@vcs0.savannah.gnu.org>
2018-12-14 23:06 ` 16/16: doc: Discourage the use of texlive as input Ludovic Courtès
2018-12-14 23:19 ` Pierre Neidhardt
2018-12-15 18:15 ` Ludovic Courtès
2018-12-15 18:23 ` Pierre Neidhardt [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=875zvusl8a.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--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 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).