public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: "Arsen Arsenović" <arsen@aarsen.me>
To: "Frank Ch. Eigler" <fche@elastic.org>
Cc: Overseers mailing list <overseers@sourceware.org>,
	Gerald Pfeifer <gerald@pfeifer.com>
Subject: Re: Please update Texinfo on gcc.gnu.org
Date: Tue, 21 Mar 2023 16:24:54 +0100	[thread overview]
Message-ID: <87y1nqgm4i.fsf@aarsen.me> (raw)
In-Reply-To: <ZBmxA68GIG/XTipn@elastic.org>

[-- Attachment #1: Type: text/plain, Size: 749 bytes --]


"Frank Ch. Eigler" <fche@elastic.org> writes:

> Hi -
>
>> I'd like to request that the server building GCC texinfo-based
>> documentation (which is, AFAIK, gcc.gnu.org) be updated to Texinfo
>> master, currently at commit f12de7a5b383bed0ea29ee34c427679e0f8b9658.
>> [...]
>> Please let me know if there's anything extra that I should do.
>
> Have you considered getting the shared gccadmin account to build &
> install its private copy of texinfo under its home directory?

That would be okay too, by my opinion (if not better, since it localizes
changes).  I don't have the power to do that myself, though, and was
asked to write to overseers, hence my email.

Thanks, have a great day.

> - FChE


-- 
Arsen Arsenović

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 251 bytes --]

  reply	other threads:[~2023-03-21 15:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-21 11:11 Arsen Arsenović
2023-03-21 13:28 ` Frank Ch. Eigler
2023-03-21 15:24   ` Arsen Arsenović [this message]
2023-03-21 23:02   ` Gerald Pfeifer
2023-03-22  0:17     ` Mark Wielaard
2023-03-22 10:39     ` Arsen Arsenović

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=87y1nqgm4i.fsf@aarsen.me \
    --to=arsen@aarsen.me \
    --cc=fche@elastic.org \
    --cc=gerald@pfeifer.com \
    --cc=overseers@sourceware.org \
    /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 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).