Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Chen Gang S <gang.chen@sunrus.com.cn>
Cc: Pedro Alves <palves@redhat.com>,
	sellcey@imgtec.com,	Jan Kratochvil <jan.kratochvil@redhat.com>,
	"Maciej W. Rozycki" <macro@linux-mips.org>,
	gdb-patches@sourceware.org, Yao Qi <yao@codesourcery.com>
Subject: Re: [Patch] Fix build problem with system call in compile/compile.c
Date: Sat, 10 Jan 2015 04:30:00 -0000	[thread overview]
Message-ID: <20150110043002.GR5445@adacore.com> (raw)
In-Reply-To: <54B04125.4050802@sunrus.com.cn>

> Excuse me, I am not quite familiar with the patch apply working flow for
> binutils/gdb, it seems each patch can only have one 'Signed-of-by' for
> it (do not like Linux kernel or QEMU, can have multiple 'Signed-of-by').
> 
> For me, this patch need multiple 'Signed-of-by': I start the patch, and
> Pedro Alves give a very necessary improvement (or it will introduce a
> new bug, which is not recognized quite obviously by others).

I know you've answered your own question about your patch in particular,
but I wanted to clarify a couple of things.

About "can only have one 'Signed-off-by'":

    We do not use git's sign-off (at least, not at the moment).
    As you know, there is an approval process through this mailing
    list which is used instead, but who actually approves the patch
    is not recorded in the git commit.

    However, the approver is not the same thing at the author, or
    the group of authors. If you are the sole author of a patch,
    and I request a few small changes that you make, and then it
    gets approved, you are still the sole author of those changes.
    Hence your name remains the only name listed in the corresponding
    ChangeLog entries. There is a small exception where a reviewer
    contributes significant ideas towards the final patch, or even
    contributes pieces of it, in which case the reviewer now also
    becomes co-author, in which case his name gets added to the
    corresponding ChangeLog entries.

> If what I said above is correct, one way maybe, apply my original patch
> firstly, then apply the fix patch by Pedro Alves. I am not quite sure
> whether this way is suitable or not, though.

About that:

    We avoid that approach, because it introduces a commit where
    we know there is an issue. Although the issue is supposed to
    get fixed right after, it still isn't great in the context of
    "git bisect" for instance.

-- 
Joel


      parent reply	other threads:[~2015-01-10  4:30 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-06  0:44 Steve Ellcey 
2015-01-06  3:09 ` Yao Qi
2015-01-06  4:16 ` Joel Brobecker
2015-01-06 16:04   ` Steve Ellcey
2015-01-07  4:14     ` Joel Brobecker
2015-01-07 18:36       ` Steve Ellcey
2015-01-07 19:01         ` Pedro Alves
2015-01-07 19:29         ` Maciej W. Rozycki
2015-01-07 19:35           ` Pedro Alves
2015-01-07 23:33             ` Maciej W. Rozycki
2015-01-08 21:12               ` Jan Kratochvil
2015-01-08 22:12                 ` Steve Ellcey
2015-01-08 23:22                   ` Pedro Alves
2015-01-09  0:10                     ` Steve Ellcey
2015-01-09  3:47                       ` Chen Gang S
2015-01-09 10:11                         ` Pedro Alves
2015-01-09 10:46                           ` Chen Gang S
2015-01-09 20:52                             ` Chen Gang S
2015-01-09 21:53                               ` Chen Gang S
2015-01-10  4:30                               ` Joel Brobecker [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=20150110043002.GR5445@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gang.chen@sunrus.com.cn \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=macro@linux-mips.org \
    --cc=palves@redhat.com \
    --cc=sellcey@imgtec.com \
    --cc=yao@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