public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Sandra Loosemore <sandra.loosemore@siemens.com>
To: "Gerald Pfeifer" <gerald@pfeifer.com>,
	"Arsen Arsenović" <arsen@aarsen.me>
Cc: gcc-patches@gcc.gnu.org, Joseph Myers <joseph@codesourcery.com>,
	Sandra Loosemore <sandra@codesourcery.com>
Subject: Re: Ping^2: [PATCH+wwwdocs 0/8] A small Texinfo refinement
Date: Thu, 23 Feb 2023 10:59:28 -0700	[thread overview]
Message-ID: <4eb0b305-0109-8d81-a0ed-19271d7adb06@siemens.com> (raw)
In-Reply-To: <6d3ede5b-d54c-eb50-5510-ecaa6d26a4e0@pfeifer.com>

On 2/22/23 18:26, Gerald Pfeifer wrote:
> On Tue, 21 Feb 2023, Arsen Arsenović wrote:
>> Ping.  Like last time, I rebased the series.
> 
> Thank you!
> 
>> The first two times around, I did not notice there's dedicated
>> maintainers for the documentation component, and so, I am adding Gerald,
>> Joseph and Sandra to CC this time.  Apologies for the omission.
> 
> Much of this is over my head in terms of texinfo, which is why I had
> to defer when I originally saw it. Sorry for not being explicit about
> that originally.
> 
> That said, I feel sufficiently confident taking care of 2/8 and 3/8
> (see my earlier replies).
> 
> I hope Sandra or Joseph will be able to help with others (especially
> 1, 5, and 6).

FYI, I am really behind on all my gcc-patches and bugzilla mail due to 
trying to finish another project that has taken way too long.  I hope to 
start digging into my backlog next week or the week after; I think I 
have a few things in the pile that ought to be addressed before gcc 13 
branches.  Anyway, this is in my queue, I just can't get to it right now.

-Sandra

      reply	other threads:[~2023-02-23 17:59 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-27  0:18 Arsen Arsenović
2023-01-27  0:18 ` [PATCH 1/7] docs: Create Indices appendix Arsen Arsenović
2023-01-27  0:18 ` [PATCH 2/7] docs: Reorder @opindex to be before corresponding options Arsen Arsenović
2023-01-27  0:18 ` [PATCH 3/7] **/*.texi: Reorder index entries Arsen Arsenović
2023-01-27 10:41   ` Iain Buclaw
2023-02-23  0:58   ` Gerald Pfeifer
2023-02-23  9:25     ` (rebased patchset) " Arsen Arsenović
2023-02-23  8:11   ` Thomas Schwinge
2023-02-23  8:44     ` Arsen Arsenović
2023-01-27  0:18 ` [PATCH 4/7] docs: Mechanically reorder item/index combos in extend.texi Arsen Arsenović
2023-01-27  0:18 ` [PATCH 5/7] doc: Add @defbuiltin family of helpers, set documentlanguage Arsen Arsenović
2023-01-27  0:18 ` [PATCH 6/7] Update texinfo.tex, remove the @gol macro/alias Arsen Arsenović
2023-01-27  0:18 ` [PATCH 7/7] update_web_docs_git: Update CSS reference to new manual CSS Arsen Arsenović
2023-01-27  0:18 ` [wwwdocs] Add revised Texinfo " Arsen Arsenović
2023-02-24  0:26   ` Gerald Pfeifer
2023-02-24  6:41     ` Arsen Arsenović
2023-01-27 12:02 ` [PATCH+wwwdocs 0/8] A small Texinfo refinement Arsen Arsenović
2023-02-23  1:13   ` Gerald Pfeifer
2023-02-13 18:51 ` Ping: " Arsen Arsenović
2023-02-21 14:59   ` Ping^2: " Arsen Arsenović
2023-02-23  1:26     ` Gerald Pfeifer
2023-02-23 17:59       ` Sandra Loosemore [this message]

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=4eb0b305-0109-8d81-a0ed-19271d7adb06@siemens.com \
    --to=sandra.loosemore@siemens.com \
    --cc=arsen@aarsen.me \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gerald@pfeifer.com \
    --cc=joseph@codesourcery.com \
    --cc=sandra@codesourcery.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 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).