From: Gerald Pfeifer <gerald@pfeifer.com>
To: Richard Biener <rguenther@suse.de>
Cc: gcc-patches@gcc.gnu.org
Subject: [wwwdocs] PATCH for Re: [PATCH] Fix my name in contrib.texi
Date: Fri, 10 Apr 2015 21:53:00 -0000 [thread overview]
Message-ID: <alpine.LSU.2.20.1504102351290.9357@tuna.site> (raw)
In-Reply-To: <alpine.LSU.2.11.1404071024290.31108@zhemvz.fhfr.qr>
On Mon, 7 Apr 2014, Richard Biener wrote:
>> htdocs/svn.html has four occurrences, and a few other pages also
>> have some. Though I don't think it's appropriate to adjust the
>> like of news.html, should I update svn.html?
> Sure, go ahead.
Done thusly.
Can you please look into mirrors.html which references your
GPG key and update that as you consider suitable?
Gerald
Index: svn.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/svn.html,v
retrieving revision 1.200
diff -u -r1.200 svn.html
--- svn.html 29 Jan 2015 08:01:07 -0000 1.200
+++ svn.html 10 Apr 2015 21:52:27 -0000
@@ -295,7 +295,7 @@
<dd>This branch is for tracking overflow behavior on expressions
rather than on types.
Patches should be marked with the tag <code>[no-undefined-overflow]</code>
- in the subject line. The branch is maintained by Richard Guenther.</dd>
+ in the subject line. The branch is maintained by Richard Biener.</dd>
<dt><a href="https://gcc.gnu.org/wiki/AndrewMacLeod/debuglocus">debuglocus</a></dt>
<dd>This branch is an experiment to see whether improved debug information
@@ -311,7 +311,7 @@
<dt>vect256</dt>
<dd>This branch is for extending vectorizer to 256bit. The branch is
- maintained by Richard Guenther and H.J. Lu. Patches should be marked
+ maintained by Richard Biener and H.J. Lu. Patches should be marked
with the tag
<code>[vect256]</code> in the subject line.</dd>
@@ -1107,14 +1107,14 @@
<dt>var-mappings-branch</dt>
<dd>This branch is for improving debug information based on tracking
multiple variables per computed value. The branch is maintained by
- Richard Guenther and Michael Matz. Patches should be marked with the
+ Richard Biener and Michael Matz. Patches should be marked with the
tag <code>[varmap]</code> in the subject line.</dd>
<dt>mem-ref</dt>
<dd>This branch is for lowering the GIMPLE IL for memory accesses to
a flat representation. See the GCC
<a href="https://gcc.gnu.org/wiki/MemRef">wiki</a> for a more detailed
- project description. The branch is maintained by Richard Guenther.
+ project description. The branch is maintained by Richard Biener.
Patches should be marked with the tag <code>[mem-ref]</code> in the
subject line.</dd>
next prev parent reply other threads:[~2015-04-10 21:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-18 12:19 Richard Biener
2014-04-06 22:15 ` Gerald Pfeifer
2014-04-07 8:26 ` Richard Biener
2015-04-10 21:53 ` Gerald Pfeifer [this message]
2015-04-13 7:29 ` [wwwdocs] PATCH for " Richard Biener
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=alpine.LSU.2.20.1504102351290.9357@tuna.site \
--to=gerald@pfeifer.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rguenther@suse.de \
/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).