all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: bo0od <bo0od@riseup.net>
Cc: 47630@debbugs.gnu.org
Subject: bug#47630: Improve guix manual installation docs
Date: Tue, 17 Aug 2021 23:28:12 +0200	[thread overview]
Message-ID: <865yw3n4lv.fsf@gmail.com> (raw)
In-Reply-To: <defe8615-0ea0-2b09-a1b3-d11593d4f315@riseup.net> (bo0od@riseup.net's message of "Thu, 15 Jul 2021 12:56:17 +0000")

Hi,

On Thu, 15 Jul 2021 at 12:56, bo0od <bo0od@riseup.net> wrote:
>> Could you propose a concrete wording solving
>> the issues you see
>
> Not really because english is not my mother tongue so there going to be errors
> in grammars, choosing of words..etc so better to be written by someone who has
> better english than me.
>
> But for the commands to go on step by step i can give that with little text
> and any webadmin can pick it up and arrange it accordingly.
>
> If guix documentation built on wikimedia it would be much easier because i can
> register and upload my changes and can be reviewed and updated, But using
> email for this is not the best way to achieve it but what to do..

Maybe you could provide what you find missing and where in the manual,
with little text.  It should be a good start for pointing what and how
to improve.


All the best,
simon




  reply	other threads:[~2021-08-17 21:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-07  4:55 bug#47630: Improve guix manual installation docs bo0od
2021-06-08 17:48 ` Eric Brown
2021-07-02 16:47 ` zimoun
2021-07-15 12:56   ` bo0od
2021-08-17 21:28     ` zimoun [this message]
2021-09-14 10:35       ` zimoun
2021-09-14 14:50         ` bo0od
2021-09-14 15:41           ` zimoun
2021-09-26  8:17             ` bo0od
2022-01-04 22:53               ` zimoun
2022-06-23  9:52                 ` zimoun
2022-06-24 10:25                   ` bo0od

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=865yw3n4lv.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=47630@debbugs.gnu.org \
    --cc=bo0od@riseup.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 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.