public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Martin Liška" <mliska@suse.cz>
To: Gerald Pfeifer <gerald@pfeifer.com>,
	Alexander Monakov <amonakov@ispras.ru>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [RFC] docs: remove documentation for unsupported releases
Date: Thu, 10 Nov 2022 09:48:44 +0100	[thread overview]
Message-ID: <e2bcaa9e-213a-7179-e7ba-eda9ce2af0cf@suse.cz> (raw)
In-Reply-To: <ef2dcd6d-76b6-5224-4dcd-4129405ec0b1@pfeifer.com>

On 11/10/22 08:29, Gerald Pfeifer wrote:
> On Wed, 9 Nov 2022, Alexander Monakov wrote:
>> For this I would suggest using the <details> tag to neatly fold links
>> for old releases. Please see the attached patch.
> 
> Loving it, Alexander!
> 
> What do you guys think about unfolding all releases we, the GCC project,
> currently support (per https://gcc.gnu.org that'd be 12.x, 11.x, and 10.x
> at this point)?

Works for me!

> 
> Either way: yes, please (aka approved). :-)

Alexander, can you please install such change?

Thanks,
Martin

> 
> On Wed, 9 Nov 2022, Martin Liška wrote:
>> I do support the patch. It should help with the Google indexing (maybe).
> 
> And thank you for raising this, Martin!
> 
> Gerald


  reply	other threads:[~2022-11-10  8:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-09 13:54 Martin Liška
2022-11-09 14:11 ` Jakub Jelinek
2022-11-09 14:17 ` Michael Matz
2022-11-09 18:57   ` Joseph Myers
2022-11-09 19:32 ` Alexander Monakov
2022-11-09 19:36   ` Martin Liška
2022-11-10  7:29     ` Gerald Pfeifer
2022-11-10  8:48       ` Martin Liška [this message]
2022-11-10 12:39         ` Alexander Monakov

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=e2bcaa9e-213a-7179-e7ba-eda9ce2af0cf@suse.cz \
    --to=mliska@suse.cz \
    --cc=amonakov@ispras.ru \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gerald@pfeifer.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).