From: "Ludovic Courtès" <ludo@gnu.org>
To: Leo Famulari <leo@famulari.name>
Cc: "Pierre-Henry Fröhring" <contact@phfrohring.com>,
53827@debbugs.gnu.org, "Maxime Devos" <maximedevos@telenet.be>
Subject: [bug#53827] [PATCH] Add a TLDR entry to the cookbook for building Guix from Git.
Date: Thu, 17 Feb 2022 11:38:03 +0100 [thread overview]
Message-ID: <87iltdok1g.fsf@gnu.org> (raw)
In-Reply-To: <Yg0jW49BK4VHlv/S@jasmine.lan> (Leo Famulari's message of "Wed, 16 Feb 2022 11:16:27 -0500")
Leo Famulari <leo@famulari.name> skribis:
> On Wed, Feb 16, 2022 at 02:36:00PM +0100, Ludovic Courtès wrote:
>> But maybe we can have both, with cross references.
>
> Sure, but we'll have to increase our efforts to maintain the cookbook.
>
> So far, we seem to forgot to update it to reflect changes in Guix, while
> we do try to keep the manual in sync with the codebase.
>
> Instead, we could put the TLDR at the beginning of the manual section
> Building From Git, and then we'll have less trouble remembering to
> update it.
Sure, why not.
Thanks,
Ludo’.
next prev parent reply other threads:[~2022-02-17 10:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-06 21:33 [bug#53827] [PATCH] Add a TLDR entry to the cookbook for building Guix from Git Pierre-Henry Fröhring
2022-02-06 22:02 ` Maxime Devos
2022-02-15 9:20 ` Ludovic Courtès
2022-02-15 10:10 ` Pierre-Henry Fröhring
2022-02-16 13:36 ` Ludovic Courtès
2022-02-16 14:36 ` zimoun
2022-02-16 15:50 ` Pierre-Henry Fröhring
2022-02-16 16:16 ` Leo Famulari
2022-02-16 20:37 ` Pierre-Henry Fröhring
2022-02-17 10:38 ` Ludovic Courtès [this message]
2022-02-06 22:02 ` Maxime Devos
2022-02-06 22:03 ` Maxime Devos
2022-02-06 22:06 ` Maxime Devos
2022-02-06 22:07 ` Maxime Devos
2022-02-06 22:09 ` Maxime Devos
2022-02-06 23:10 ` Pierre-Henry Fröhring
2022-02-06 23:03 ` [bug#53827] [PATCH] Add a TLDR entry " Pierre-Henry Fröhring
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=87iltdok1g.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=53827@debbugs.gnu.org \
--cc=contact@phfrohring.com \
--cc=leo@famulari.name \
--cc=maximedevos@telenet.be \
/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.