public inbox for
help / color / mirror / Atom feed
From: Ramana Radhakrishnan <>
Subject: gcc-wwwdocs branch master updated. 4e5f373406ed5da42c4a7c4b7f650d92195f2984
Date: Fri,  4 Nov 2022 09:51:07 +0000 (GMT)	[thread overview]
Message-ID: <> (raw)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gcc-wwwdocs".

The branch, master has been updated
       via  4e5f373406ed5da42c4a7c4b7f650d92195f2984 (commit)
      from  d41f7632f1b6f0fbdebb5b7c9ef27055264b4018 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 4e5f373406ed5da42c4a7c4b7f650d92195f2984
Author: Ramana Radhakrishnan <>
Date:   Fri Nov 4 09:30:00 2022 +0000

    Update affiliation

diff --git a/htdocs/steering.html b/htdocs/steering.html
index 3a38346d..95d6a4a8 100644
--- a/htdocs/steering.html
+++ b/htdocs/steering.html
@@ -38,7 +38,7 @@ place to reach them is the gcc <a href="lists.html">mailing list</a>.</p>
 <li>Toon Moene (Koninklijk Nederlands Meteorologisch Instituut)</li>
 <li>Joseph Myers (CodeSourcery / Mentor Graphics) [co-Release Manager]</li>
 <li>Gerald Pfeifer (SUSE)</li>
-<li>Ramana Radhakrishnan (ARM)</li>
+<li>Ramana Radhakrishnan </li>
 <li>Joel Sherrill (OAR Corporation)</li>
 <li>Ian Lance Taylor (Google)</li>
 <li>Jim Wilson (SiFive)</li>


Summary of changes:
 htdocs/steering.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


                 reply	other threads:[~2022-11-04  9:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).