From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sourceware.org
Cc: Pedro Alves <palves@redhat.com>, Mark Rages <markrages@gmail.com>
Subject: Re: [PATCH] Re: Flash memory size not aligned to address
Date: Wed, 11 Oct 2017 15:54:00 -0000 [thread overview]
Message-ID: <20171011085355.78e0466e@pinnacle.lan> (raw)
In-Reply-To: <684fd87f-3a01-0725-6b75-bb4bd4aad367@redhat.com>
On Wed, 11 Oct 2017 10:31:08 +0100
Pedro Alves <palves@redhat.com> wrote:
> On 10/11/2017 08:56 AM, Kevin Buettner wrote:
> > On Mon, 9 Oct 2017 13:08:44 -0600
> > Mark Rages <markrages@gmail.com> wrote:
> >
> >> On Mon, Oct 9, 2017 at 11:51 AM, Kevin Buettner <kevinb@redhat.com> wrote:
> >>>
> >>> Please let us know if you intend to pursue a copyright assignment.
> >>> If not, I can commit/push this change for you.
> >>
> >> I am not pursuing copyright assignment right now. Please push this
> >> patch for me.
> >
> > I've pushed it for you. The ChangeLog entry is attributed to you. The
> > git commit has my name on it, but I indicate where the patch came
> > from in the commit comment.
> >
> > (I hope that's the correct procedure...)
>
> Actually, the right procedure is to amend to commit's authorship too.
> There are useful instructions here:
>
> https://sourceware.org/glibc/wiki/GlibcGit#Author_Attribution
Okay, thanks.
I gather it too late to amend it now, right? (Since git commit --amend
only works on the most recent commit.)
Kevin
next prev parent reply other threads:[~2017-10-11 15:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-05 21:49 Mark Rages
2017-10-07 18:36 ` [PATCH] " Mark Rages
2017-10-07 21:42 ` Kevin Buettner
2017-10-09 16:28 ` Mark Rages
2017-10-09 17:51 ` Kevin Buettner
2017-10-09 19:08 ` Mark Rages
2017-10-11 7:56 ` Kevin Buettner
2017-10-11 9:31 ` Pedro Alves
2017-10-11 15:54 ` Kevin Buettner [this message]
2017-10-11 16:11 ` Pedro Alves
2017-10-11 16:27 ` Kevin Buettner
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=20171011085355.78e0466e@pinnacle.lan \
--to=kevinb@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=markrages@gmail.com \
--cc=palves@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