From: "Gábor Boskovits" <boskovits@gmail.com>
To: Laura Lazzati <laura.lazzati.15@gmail.com>
Cc: Guix-devel <guix-devel@gnu.org>,
Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Subject: Re: Trying to make texinfo patch
Date: Mon, 5 Nov 2018 09:24:17 +0100 [thread overview]
Message-ID: <CAE4v=piCdkuKACWX3MFkf+F_Gc-kV4mij+gQQsxvU4YURypJig@mail.gmail.com> (raw)
In-Reply-To: <CAPNLzUNiGSqeys_kH_+crnxadchHpbJ0cztOjf=5fPLNcO2bDg@mail.gmail.com>
Hello Laura,
Laura Lazzati <laura.lazzati.15@gmail.com> ezt írta (időpont: 2018.
nov. 5., H, 2:35):
>
> Hi!
> I am writing a new thread so that it does not end up messy.
> Yesterday and today I've been reading and adding @cindex to guix.texi to make a new patch. I know that you don't mind that much about the number of contributions, but it was for myself mostly, to learn texinfo and to see how it applies to documentation.
> I just added a few @cindex at the very beginning of the guix.texi file, to see if it is OK. But had some trouble with makeinfo, I was getting this kind of errors: https://paste.debian.net/1050349/.
> Regards!
> Laura
>
Building the manual is a more sophisticated process, the first error
you see is because the manual is not composed of only one file, and
some files seem to be missing.
I don't know if we currently have a top level Makefile target to build
the manual only, but simply make-ing in the source tree rebuilds the
manual. I believe that is the simplest
way to test changes.
Best regards,
g_bor
next prev parent reply other threads:[~2018-11-05 8:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 1:34 Trying to make texinfo patch Laura Lazzati
2018-11-05 8:24 ` Gábor Boskovits [this message]
2018-11-06 1:44 ` Laura Lazzati
2018-11-06 8:15 ` Gábor Boskovits
2018-11-06 13:16 ` Laura Lazzati
2018-11-06 17:53 ` Thorsten Wilms
2018-11-06 19:44 ` Leo Famulari
2018-11-07 14:35 ` Laura Lazzati
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='CAE4v=piCdkuKACWX3MFkf+F_Gc-kV4mij+gQQsxvU4YURypJig@mail.gmail.com' \
--to=boskovits@gmail.com \
--cc=guix-devel@gnu.org \
--cc=laura.lazzati.15@gmail.com \
--cc=ricardo.wurmus@mdc-berlin.de \
/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.