unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Thompson, David" <dthompson2@worcester.edu>
To: Leo Famulari <leo@famulari.name>
Cc: 22687@debbugs.gnu.org
Subject: bug#22687: Online manual not updated automatically
Date: Mon, 15 Feb 2016 17:49:17 -0500	[thread overview]
Message-ID: <CAJ=RwfYs+5d5o61Zd_wVdXKmw26OZN87CuGbiGd8BN=Vv_vS+w@mail.gmail.com> (raw)
In-Reply-To: <20160215215024.GA22646@jasmine>

On Mon, Feb 15, 2016 at 4:50 PM, Leo Famulari <leo@famulari.name> wrote:
> ----- Forwarded message from carl hansen <carlhansen1234@gmail.com> -----
>  http://www.gnu.org/software/guix/manual/
> works.
> BUT
> it says:
> "last updated November 04, 2015"
> So cronjob on gnu.org that updates to the lastest version is not working.
> Might
> be the answer to the problem about , too.
>
> ----- End forwarded message -----
>
> I see the value of the online manual matching the version of the Guix
> binaries we distribute, but on the other hand, we get a lot of questions
> that are answered in the latest version of the manual.
>
> Thoughts?

IMO, this is a "wontfix", but let's see what everyone else thinks.

- Dave

  reply	other threads:[~2016-02-15 22:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-15 21:50 bug#22687: Online manual not updated automatically Leo Famulari
2016-02-15 22:49 ` Thompson, David [this message]
2016-02-16 10:06 ` Ricardo Wurmus
2016-02-16 16:25   ` Andreas Enge
2016-02-16 16:33     ` Ricardo Wurmus
2016-02-16 16:42       ` Andreas Enge
2016-02-16 17:14         ` Florian Paul Schmidt
2016-02-16 20:37           ` Mathieu Lirzin
2016-02-21 22:41             ` Ludovic Courtès
2016-02-17  4:07   ` Chris Marusich
2016-02-18  9:38     ` Alex Kost
2016-02-21 22:43   ` Ludovic Courtès
2018-12-17 10:52 ` Julien Lepiller
2018-12-17 11:28   ` Ricardo Wurmus
2019-07-31 15:31 ` Julien Lepiller
2019-07-31 17:46   ` Leo Famulari

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='CAJ=RwfYs+5d5o61Zd_wVdXKmw26OZN87CuGbiGd8BN=Vv_vS+w@mail.gmail.com' \
    --to=dthompson2@worcester.edu \
    --cc=22687@debbugs.gnu.org \
    --cc=leo@famulari.name \
    /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).