From: Jonathan Wakely <jwakely@redhat.com>
To: "Eric S. Raymond" <esr@thyrsus.com>
Cc: Joseph Myers <joseph@codesourcery.com>,
Sandra Loosemore <sandra@codesourcery.com>,
gcc-patches@gcc.gnu.org, libstdc++ <libstdc++@gcc.gnu.org>
Subject: Re: [PATCH] Clean up references to Subversion in documentation sources.
Date: Mon, 13 Jan 2020 18:12:00 -0000 [thread overview]
Message-ID: <20200113173523.GD60955@redhat.com> (raw)
In-Reply-To: <20200113172455.GA88155@thyrsus.com>
On 13/01/20 12:24 -0500, Eric S. Raymond wrote:
>Joseph Myers <joseph@codesourcery.com>:
>> 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'm hesitant to request push access this soon, but...you don't seem to
>have an MR capability, and I have some other housekeeping/documentation
>patches in mind.
Email the patches to gcc-patches@gcc.gnu.org, that's how things get
merged.
We're not looking to change any workflows now.
next prev parent reply other threads:[~2020-01-13 17:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200113140202.GA63759@thyrsus.com>
2020-01-13 16:13 ` Sandra Loosemore
2020-01-13 16:21 ` Joseph Myers
2020-01-13 17:35 ` Eric S. Raymond
2020-01-13 18:12 ` Jonathan Wakely [this message]
2020-01-13 21:41 ` Eric S. Raymond
2020-01-28 13:28 ` Segher Boessenkool
2020-01-20 8:24 ` Sandra Loosemore
2020-01-21 22:27 ` Jonathan Wakely
2020-01-13 16:49 ` Jonathan Wakely
2020-01-13 17:24 ` Jonathan Wakely
2020-01-14 16:50 ` Gerald Pfeifer
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=20200113173523.GD60955@redhat.com \
--to=jwakely@redhat.com \
--cc=esr@thyrsus.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=libstdc++@gcc.gnu.org \
--cc=sandra@codesourcery.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).