From: jgart <jgart@dismail.de>
To: pinoaffe <pinoaffe@airmail.cc>
Cc: guix-devel@gnu.org
Subject: Re: Texinfo, Free Beer
Date: Tue, 9 Aug 2022 18:03:01 -0500 [thread overview]
Message-ID: <20220809180301.GB19246@gac> (raw)
In-Reply-To: <871qtpsr9q.fsf@airmail.cc>
On Tue, 09 Aug 2022 11:22:02 +0200 pinoaffe <pinoaffe@airmail.cc> wrote:
> So far, whenever I wrote texinfo, I'd do so purely by mimicry of
> surrounding documentation, and that's rather sub-optimal.
Likewise, that's been my approach too mostly.
prev parent reply other threads:[~2022-08-09 23:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-06 13:30 Texinfo, Free Beer jgart
2022-08-06 13:43 ` Ekaitz Zarraga
2022-08-09 9:22 ` pinoaffe
2022-08-09 23:03 ` jgart [this message]
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=20220809180301.GB19246@gac \
--to=jgart@dismail.de \
--cc=guix-devel@gnu.org \
--cc=pinoaffe@airmail.cc \
/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).