Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Keith Seitz <keiths@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH v6 00/11] c++/14441: Rvalue reference support
Date: Mon, 13 Mar 2017 18:51:00 -0000	[thread overview]
Message-ID: <bfa546df-2f2f-40a4-41d4-f48159b1df3e@redhat.com> (raw)
In-Reply-To: <1489176286-27973-1-git-send-email-keiths@redhat.com>

On 03/10/2017 08:04 PM, Keith Seitz wrote:
> This patch series was submitted in June, 2016, and the original author does
> not have the time to see this through. Given that we would like this in the
> 8.0 release, I have contacted the orginal author, who is allowing me to
> champion his patch on his behalf.
> 
> When this series was last reviewed, revisions were requested in patches 8
> and 11. I have highlighted in those patches what I have changed over the last
> submitted patch version (v5).

Thanks so much for this Keith.

I'll point out a few nits to patch #11, but otherwise the
series is OK.

Before committing, please address a couple procedural issues.

> +2017-MM-DD  Keith Seitz  <keiths@redhat.com>
> +
> +	PR gdb/14441
> +	From Artemiy Volkov  <artemiyv@acm.org>

As explained in:

 https://www.gnu.org/prep/standards/standards.html#Style-of-Change-Logs

Since the patch is unchanged, this should be written as:

2017-MM-DD  Artemiy Volkov  <artemiyv@acm.org>

	PR gdb/14441

Likewise in the other patches, of course.

Likewise, the git commit "Author" should be preserved when
it makes sense.  For the patches that are largely unchanged
from Artemiy's original versions, we should make sure that
our git history preserves his authorship.

When changes were done to the patches to fix things, to
apply modernization, etc., add your name as another author
for the patch, like:

YYYY-MM-DD  Hacker 1  <hacker2@foo.com>
	    Hacker 2  <hacker2@bar.com>

For example, in patch #8, the ChangeLog entry for
the manual should be "squashed", and then both names
should appear as above, instead of keeping the "who did what"
parts separated.

Thanks,
Pedro Alves


      parent reply	other threads:[~2017-03-13 18:51 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-10 20:04 Keith Seitz
2017-03-10 20:04 ` [PATCH v6 01/11] Add definitions for rvalue reference types Keith Seitz
2017-03-10 20:05 ` [PATCH v6 03/11] Add ability to return rvalue reference values from value_ref Keith Seitz
2017-03-10 20:05 ` [PATCH v6 11/11] Add rvalue reference tests and NEWS entry Keith Seitz
2017-03-10 22:02   ` Eli Zaretskii
2017-03-14 18:14     ` Keith Seitz
2017-03-17 17:06     ` Keith Seitz
2017-03-17 18:51       ` Eli Zaretskii
2017-03-13 18:52   ` Pedro Alves
2017-03-14 18:15     ` Keith Seitz
2017-03-14 18:39       ` Pedro Alves
2017-04-04 11:10   ` Yao Qi
2017-03-10 20:05 ` [PATCH v6 02/11] Change {lookup,make}_reference_type API Keith Seitz
2017-03-10 20:10 ` [PATCH v6 04/11] Support rvalue reference type in parser Keith Seitz
2017-03-10 20:10 ` [PATCH v6 08/11] Support rvalue references in the gdb python module (includes doc/) Keith Seitz
2017-03-10 22:04   ` Eli Zaretskii
2017-03-14 18:14     ` Keith Seitz
2017-03-17 17:06     ` Keith Seitz
2017-03-17 18:51       ` Eli Zaretskii
2017-03-10 20:10 ` [PATCH v6 05/11] Implement demangling for rvalue reference type names Keith Seitz
2017-03-10 20:10 ` [PATCH v6 07/11] Support DW_TAG_rvalue_reference type Keith Seitz
2017-03-10 20:10 ` [PATCH v6 06/11] Implement printing of rvalue reference types and values Keith Seitz
2017-03-10 20:12 ` [PATCH v6 09/11] Convert lvalue reference type check to general reference type check Keith Seitz
2017-03-10 20:14 ` [PATCH v6 10/11] Add rvalue references to overloading resolution Keith Seitz
2017-03-13 18:51 ` Pedro Alves [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=bfa546df-2f2f-40a4-41d4-f48159b1df3e@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=keiths@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