From: Gerald Pfeifer <gerald@pfeifer.com>
To: "Frank Ch. Eigler" <fche@elastic.org>
Cc: overseers@sourceware.org, "Arsen Arsenović" <arsen@aarsen.me>
Subject: Re: Please update Texinfo on gcc.gnu.org
Date: Wed, 22 Mar 2023 00:02:33 +0100 (CET) [thread overview]
Message-ID: <0b0d7974-fda0-ea5f-ac11-95ae43faa32e@pfeifer.com> (raw)
In-Reply-To: <ZBmxA68GIG/XTipn@elastic.org>
On Tue, 21 Mar 2023, Frank Ch. Eigler wrote:
>> 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?
I'm not sure how broadly we want to provide access to the gccadmin
account, software supply chain and such? (In general, not particular
to Arsen at all!)
I'll try to have a look at installing an updated version of Texinfo
and how to use it for our daily doc builds this coming weekend...
(Not a big fan of using "random" Git versions in production, though;
any chance for a regular release coming soon?)
Gerald
next prev parent reply other threads:[~2023-03-21 23:02 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ć
2023-03-21 23:02 ` Gerald Pfeifer [this message]
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=0b0d7974-fda0-ea5f-ac11-95ae43faa32e@pfeifer.com \
--to=gerald@pfeifer.com \
--cc=arsen@aarsen.me \
--cc=fche@elastic.org \
--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).