All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Glenn Washburn <development@efficientek.com>
Cc: Daniel Kiper <dkiper@net-space.pl>,
	The development of GNU GRUB <grub-devel@gnu.org>,
	xxc3ncoredxx@gmail.com
Subject: Re: [PATCH v3] docs: Add debugging chapter to development documentation
Date: Tue, 15 Aug 2023 22:37:08 +0200	[thread overview]
Message-ID: <20230815223708.779e712d.olaf@aepfle.de> (raw)
In-Reply-To: <20230815123129.57bc8207@crass-HP-ZBook-15-G2>


[-- Attachment #1.1: Type: text/plain, Size: 434 bytes --]

Tue, 15 Aug 2023 12:31:29 -0500 Glenn Washburn <development@efficientek.com>:

> I'm not seeing this issue when building on Debian 11. I'm successfully
> building the info, html, and pdf documentation from the texi files
> using debians texinfo package at version 6.7.0.dfsg.2-6. Are you sure
> you are building from clean sources? What version of texinfo are you at?

The sources are clean, makeinfo 4.13a is used.


Olaf

[-- Attachment #1.2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 141 bytes --]

_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel

  reply	other threads:[~2023-08-15 20:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-06  5:48 [PATCH v3] docs: Add debugging chapter to development documentation Glenn Washburn
2023-06-12 14:48 ` Daniel Kiper
2023-06-15  6:21 ` Oskari Pirhonen
2023-06-15 11:06   ` Daniel Kiper
2023-06-16  2:19     ` Oskari Pirhonen
2023-08-15  8:14     ` Olaf Hering
2023-08-15 17:31       ` Glenn Washburn
2023-08-15 20:37         ` Olaf Hering [this message]
2023-08-16  5:29           ` Glenn Washburn
2023-08-16  8:41             ` Olaf Hering
2023-08-16 17:53               ` Glenn Washburn
2023-08-17  9:03                 ` Olaf Hering

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=20230815223708.779e712d.olaf@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=development@efficientek.com \
    --cc=dkiper@net-space.pl \
    --cc=grub-devel@gnu.org \
    --cc=xxc3ncoredxx@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. 
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.