all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: “guix --help” should point to https://guix.gnu.org/help/
Date: Mon, 25 May 2020 11:17:55 +0200	[thread overview]
Message-ID: <CAJ3okZ3MoS=mRSyn6C=Mse=ZWSu=0yeGmtW4FE7nXh5SOBZgbw@mail.gmail.com> (raw)
In-Reply-To: <87a71xyr77.fsf@gnu.org>

Hi Ludo,

On Sun, 24 May 2020 at 23:10, Ludovic Courtès <ludo@gnu.org> wrote:

> This is harsh, maybe unnecessarily so, but still a very valid criticism
> of that page.  I guess that page was created with good intentions, but
> it’s pretty much useless indeed.  :-/

I am sorry if I have been harsh and if I have hurt someone.  I was
*not* my intention.  Otherwise, I would not spend 5 minutes to follow
all the links and check how to reach help for the GNU Guix project
from this webpage. :-)


> Probably we should work on the GNU side to make that page more useful,
> but we should also definitely print the relevant Guix URL.

Yes, we should.  However, to be honest, reading GNU related mailing
lists over the last past months and especially the recent emacs-devel
threads, I do not personally have enough energy to potentially argue
the obvious on bikeshed.


Cheers,
simon


  parent reply	other threads:[~2020-05-25  9:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-15 10:18 “guix --help” should point to https://guix.gnu.org/help/ Ricardo Wurmus
2020-05-15 11:00 ` zimoun
2020-05-15 15:54   ` Diego Nicola Barbato
2020-05-17 23:01     ` Ludovic Courtès
2020-05-18  9:10       ` Pierre Neidhardt
2020-05-15 20:22   ` Bengt Richter
2020-05-17 23:03 ` Ludovic Courtès
2020-05-20 15:36 ` zimoun
2020-05-24 21:10   ` Ludovic Courtès
2020-05-25  6:40     ` Efraim Flashner
2020-05-25  9:17     ` zimoun [this message]
2020-05-25 21:24       ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJ3okZ3MoS=mRSyn6C=Mse=ZWSu=0yeGmtW4FE7nXh5SOBZgbw@mail.gmail.com' \
    --to=zimon.toutoune@gmail.com \
    --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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.