unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Pierre Neidhardt <mail@ambrevar.xyz>, 32845@debbugs.gnu.org
Subject: bug#32845: guix.info: Missing manual
Date: Thu, 27 Sep 2018 15:46:23 +0200	[thread overview]
Message-ID: <87ftxv3vf4.fsf@gnu.org> (raw)
In-Reply-To: <87zhw4rpel.fsf@elephly.net> (Ricardo Wurmus's message of "Wed, 26 Sep 2018 22:10:10 +0200")

Hello,

Ricardo Wurmus <rekado@elephly.net> skribis:

> The copy at guix.info does not use the same gnu.org/software/guix
> prefix, so all links to the manual are likely wrong.
>
> This needs to be fixed in our website code, so that the same code works
> for both sites.

I wonder what should be done with guix.info: should we keep it as a
mirror, or should it redirect to gnu.org, or the opposite?

My initial plan was to use guix.gnu.org as the primary domain but we’re
stuck with the “Let’s Encrypt vs. multiple entries in DNS A records”
issue.  At the same time, guix.info works just fine.

Thoughts?

Ludo’.

  reply	other threads:[~2018-09-27 13:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-26 10:33 bug#32845: guix.info: Missing manual Pierre Neidhardt
2018-09-26 18:01 ` Ricardo Wurmus
2018-09-26 19:44   ` Pierre Neidhardt
2018-09-26 20:10     ` Ricardo Wurmus
2018-09-27 13:46       ` Ludovic Courtès [this message]
2018-09-27 15:28         ` Ricardo Wurmus
2018-09-27 17:37           ` Pierre Neidhardt
2018-09-28 20:08             ` Ludovic Courtès
2018-09-28 20:03           ` Ludovic Courtès
2018-09-28 20:38             ` Ricardo Wurmus
2018-09-28 20:39             ` Tobias Geerinckx-Rice
2018-09-29 16:14               ` Ludovic Courtès
2020-01-25 18:00 ` sirgazil via Bug reports for GNU Guix
2020-01-28 10:28   ` 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=87ftxv3vf4.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=32845@debbugs.gnu.org \
    --cc=mail@ambrevar.xyz \
    --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).