From: Ricardo Wurmus <rekado@elephly.net>
To: quiliro@fsfla.org
Cc: help-guix@gnu.org
Subject: Re: how to translate info guix to text file or pdf or html ?
Date: Fri, 29 Mar 2019 04:00:22 +0100 [thread overview]
Message-ID: <87h8bm1j21.fsf@elephly.net> (raw)
In-Reply-To: <cffef0bbc936cf3a132d5970d9811dbc@riseup.net>
Quiliro Ordonez <quiliro@riseup.net> writes:
> El 2019-03-28 20:29, Ricardo Wurmus escribió:
>> Joshua Branson <jbranso@dismail.de> writes:
>>
>>> Guix's manual changes
>>> all the time. Trying to keep the website up-to-date is a tough task.
>>
>> It is a decision, not a technical limitation. We want the public copy
>> of the manual to match the latest release, not an arbitrary later
>> version.
>
> Sounds reasonable.
>
> So, would a link to an "alfa" version be possible to place on the web?
> Is it complicated to generate automatically each day with a cron job?
I wanted to always show the latest manual on guix.info (where it’s
easier for us to update the pages), but I haven’t gotten around to doing
that yet.
--
Ricardo
prev parent reply other threads:[~2019-03-29 3:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-27 19:15 how to translate info guix to text file or pdf or html ? znavko
2019-03-28 18:52 ` Oleg Pykhalov
2019-03-28 19:11 ` Quiliro Ordonez
2019-03-28 20:31 ` Ricardo Wurmus
2019-03-29 9:45 ` znavko
2019-03-29 9:47 ` znavko
2019-03-29 13:40 ` Joshua Branson
2019-03-28 19:30 ` Joshua Branson
2019-03-28 20:29 ` Ricardo Wurmus
2019-03-28 22:41 ` Quiliro Ordonez
2019-03-29 3:00 ` Ricardo Wurmus [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=87h8bm1j21.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=help-guix@gnu.org \
--cc=quiliro@fsfla.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.
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).