From: Sandra Loosemore <sandra@codesourcery.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: "Eric S. Raymond" <esr@thyrsus.com>, <gcc-patches@gcc.gnu.org>,
libstdc++ <libstdc++@gcc.gnu.org>
Subject: Re: [PATCH] Clean up references to Subversion in documentation sources.
Date: Mon, 20 Jan 2020 04:40:00 -0000 [thread overview]
Message-ID: <afa2c5fb-213c-62d5-4957-00903a4124cf@codesourcery.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2001131612030.11452@digraph.polyomino.org.uk>
On 1/13/20 9:12 AM, Joseph Myers wrote:
> On Mon, 13 Jan 2020, Sandra Loosemore wrote:
>
>> On 1/13/20 7:02 AM, Eric S. Raymond wrote:
>>> Clean up references to SVN in in the GCC docs, redirecting to Git
>>> documentation as appropriate.
>>
>> This is OK, although the set of changes for the libstdc++ manual like this
>> gave me pause:
>
> I think you'll need to commit this for Eric (using --author= to set the
> git author, whenever you commit a patch for someone else). The libstdc++
> maintainers can probably handle regenerating the HTML version of the
> libstdc++ documentation.
I've pushed this patch to mainline and the gcc8 and gcc9 branches now.
-Sandra
next prev parent reply other threads:[~2020-01-20 3:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-13 16:09 Eric S. Raymond
2020-01-13 16:21 ` Sandra Loosemore
2020-01-13 16:40 ` Joseph Myers
2020-01-13 17:35 ` Eric S. Raymond
2020-01-13 18:06 ` Jonathan Wakely
2020-01-13 18:38 ` Eric S. Raymond
2020-01-27 20:11 ` Segher Boessenkool
2020-01-20 4:40 ` Sandra Loosemore [this message]
2020-01-20 23:05 ` Jonathan Wakely
2020-01-13 17:12 ` Jonathan Wakely
2020-01-13 17:27 ` Jonathan Wakely
2020-01-14 11:46 ` Gerald Pfeifer
2020-01-15 21:52 ` Jonathan Wakely
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=afa2c5fb-213c-62d5-4957-00903a4124cf@codesourcery.com \
--to=sandra@codesourcery.com \
--cc=esr@thyrsus.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=libstdc++@gcc.gnu.org \
/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).