From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: texlive-fetch instead of svn-fetch
Date: Fri, 01 Mar 2019 16:32:06 +0100 [thread overview]
Message-ID: <8736o6fw5l.fsf@ambrevar.xyz> (raw)
In-Reply-To: <87imx2y5qg.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 240 bytes --]
Thanks for clarifying this.
Then I 100% agree with your approach.
I should have a little bit more free time in the coming days, so I'll (finally)
get down to write the tlpdb importer :)
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-03-01 15:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-01 14:50 texlive-fetch instead of svn-fetch Ricardo Wurmus
2019-03-01 14:58 ` Pierre Neidhardt
2019-03-01 15:27 ` Ricardo Wurmus
2019-03-01 15:32 ` Pierre Neidhardt [this message]
2019-03-06 14:55 ` Ludovic Courtès
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=8736o6fw5l.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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).