From: Gerald Pfeifer <gerald@pfeifer.com>
To: Tobias Burnus <Tobias_Burnus@mentor.com>
Cc: Jakub Jelinek <jakub@redhat.com>, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [wwwdocs][Patch] Add OpenMP by-GCC-version implementation status
Date: Mon, 16 May 2022 12:06:20 +0200 (CEST) [thread overview]
Message-ID: <e5681d5a-80d0-7e8e-3bd4-5455eaf9794c@pfeifer.com> (raw)
In-Reply-To: <798bc8e6-567b-5ed6-e298-655948e89f5e@mentor.com>
Hi Tobias,
On Sat, 14 May 2022, Tobias Burnus wrote:
> Jakub and I discussed the other day that it would be useful
> to have a page similar to
> https://gcc.gnu.org/projects/cxx-status.html
> to provide by-GCC-version information of the which OpenMP are supported.
this looks like a great idea, thanks!
> Comments regarding the file, where it is placed and how it is linked to?
> I found it simpler to have a single very long line rather than trying
> to break it into 80-character lines, but I can also do this reformatting.
Yes, in cases like this with a small and fixed set of contributors (to
that table) ... whatever serves you best.
Regarding the name projects/gomp/openmp-status.html feels a bit long?
How about
projects/gomp/status.html
? Or maybe even make this part of the main index.html page, so
projects/gomp/
in the browser? The former is more of a stronger recommendation, the
latter just a thought.
Minor tweak: it's "to file a bug report", so "filing a bug" not "filling a
bug", though indeed when filing a bug report one needs to fill a form. :-)
Gerald
prev parent reply other threads:[~2022-05-16 10:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-14 21:27 Tobias Burnus
2022-05-16 9:42 ` Tobias Burnus
2022-05-17 7:54 ` Gerald Pfeifer
2022-05-17 8:21 ` Jakub Jelinek
2022-05-17 8:49 ` Tobias Burnus
2022-05-17 9:00 ` Jakub Jelinek
2022-05-17 9:50 ` Tobias Burnus
2022-05-17 10:02 ` Jakub Jelinek
2023-01-21 20:57 ` Gerald Pfeifer
2022-05-16 10:06 ` Gerald Pfeifer [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=e5681d5a-80d0-7e8e-3bd4-5455eaf9794c@pfeifer.com \
--to=gerald@pfeifer.com \
--cc=Tobias_Burnus@mentor.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.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).