From: Simon Tournier <zimon.toutoune@gmail.com>
To: "Maxim Cournoyer" <maxim.cournoyer@gmail.com>,
"Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org, 58813@debbugs.gnu.org
Subject: Re: bug#58813: can't substitute etc/teams.scm command as doc suggests
Date: Wed, 11 Jan 2023 16:20:01 +0100 [thread overview]
Message-ID: <865ydd5c9q.fsf@gmail.com> (raw)
In-Reply-To: <87358jmnwj.fsf@gmail.com>
Hi,
On Mon, 09 Jan 2023 at 15:52, Maxim Cournoyer <maxim.cournoyer@gmail.com> wrote:
> It wouldn't change; patman would be hinted at briefly with a reference
> to its documentation (info '(u-boot) Patman patch manager' from the
> u-boot-documentation package) as a nice way to stay organize with
> submissions and automate a few things on top of git send-email.
Is it possible to read online patman documentation? I am not able to
find one. Moreover, it could ease the adoption if a minimal sample of
such configuration is provided. A minimal out of the box configuration
as starter.
On my side, if I have to do more than just click to read documentation,
then I give up. And then, if I have to parse lengthy documentation,
then it depends on my motivation but it is also possible that I give
up–the well-known RTFM trap. In other words, I am lazy. :-)
Cheers,
simon
next prev parent reply other threads:[~2023-01-11 16:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 22:29 Bogus ‘etc/teams.scm’ usage recommendations? Ludovic Courtès
2023-01-05 12:21 ` Simon Tournier
2023-01-05 17:03 ` Maxim Cournoyer
2023-01-05 17:03 ` bug#58813: " Maxim Cournoyer
2023-01-09 17:23 ` bug#58813: can't substitute etc/teams.scm command as doc suggests Ludovic Courtès
2023-01-09 20:52 ` Maxim Cournoyer
2023-01-11 15:20 ` Simon Tournier [this message]
2023-01-12 3:00 ` Maxim Cournoyer
2023-01-12 13:31 ` Simon Tournier
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=865ydd5c9q.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=58813@debbugs.gnu.org \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=maxim.cournoyer@gmail.com \
/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).