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: Tue, 6 Nov 2018 09:15:48 +0100 [thread overview]
Message-ID: <CAE4v=pg+BRjYQEFJ3a_RnK7nD=yrs0BgRSWEZebB9nQETKesCQ@mail.gmail.com> (raw)
In-Reply-To: <CAPNLzUNmnkfegb1eoOf-1ZQMavq_PtR6nmkNGP+0nE7vzC8ZhA@mail.gmail.com>
Hello Laura,
Laura Lazzati <laura.lazzati.15@gmail.com> ezt írta (időpont: 2018.
nov. 6., K, 2:44):
>
>
>> 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.
>
> I tried to explain what I did on IRC. In the end I just git pulled and got the new version of the guix.texi file.
> Ran make again in the source tree - helped me to recall some useful Makefile concepts. And added just the few cindex again, they are not many, but to check that I learned texinfo.
> Then, since in guix.info website I had the full html version, ran:
> makeinfo --html --nosplit guix.texi and got a similar html file that looked similar to the original one, nut with the index entries updated.
Ok.
> And I don't know if I should write this in guix-devel, there is a bug list - it's almost my time to go to bed, but I recall seing it - where I was mentioning that in guix.info site the references to documentation have html_node in their path and they return a 404 not found when clicking them.
You can report that to the bugs list.
> Tomorrow I will try to send the patch.
> I have some questions to ask you:
> 1) I got an Ourteachy reminder about recording my Application form. I guess it was just a reminder, but please let me know if it you got it.
From here it looks fine.
> 2) I was suggested to have at least for a my foreing distro and guix package manager an aws account, in case something happens to my computer. I don't know if it is accepted by the community.
I am confused, could you please rephrase this question?
> 3) Is it OK if I write daily telling you what I will be doing/ did that day, and what I am learning if the number of contributions don't count that much? Maybe it is more useful that.
Yes a daily report is fine, we found from earlier expericence that a
report at least two times a week is really important in these types of
projects.
>
> Regards!
> Laura
>
>
>
Best regards,
g_bor
next prev parent reply other threads:[~2018-11-06 8:19 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
2018-11-06 1:44 ` Laura Lazzati
2018-11-06 8:15 ` Gábor Boskovits [this message]
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=pg+BRjYQEFJ3a_RnK7nD=yrs0BgRSWEZebB9nQETKesCQ@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.