From: "J.W. Jagersma" <jwjagersma@gmail.com>
To: Nick Clifton <nickc@redhat.com>
Cc: binutils@sourceware.org, stsp@users.sourceforge.net, dj@delorie.com
Subject: Re: [PATCH 0/3] coff-go32-exe: support variable-length stubs
Date: Wed, 1 Apr 2020 18:45:51 +0200 [thread overview]
Message-ID: <0eebb21e-11b1-c267-0782-0ebc8d5af346@gmail.com> (raw)
In-Reply-To: <c197817a-8ed9-ce50-23ea-79a3037fe9d9@redhat.com>
On 2020-03-20 15:04, Nick Clifton wrote:
> Hi Jan
>
>> This series includes three patches:
>
> Thank you for submitting these patches. Before we can accept them
> however we will need an FSF copyright assignment in place from you.
>
> Please could you fill out the form here and email it off to the FSF
> in order to start the process:
>
> http://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=blob_plain;f=doc/Copyright/request-assign.changes;hb=HEAD
>
> Cheers
> Nick
Copyright assignment has been signed, these patches are now ready for review.
next prev parent reply other threads:[~2020-04-01 16:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-19 19:19 J.W. Jagersma
2020-03-19 19:19 ` [PATCH 1/3] always add base bfd->origin to file offset J.W. Jagersma
2020-03-19 19:19 ` [PATCH 2/3] coff-go32-exe: support variable-length stubs J.W. Jagersma
2020-03-19 19:19 ` [PATCH 3/3] normalize names in coff-stgo32.c J.W. Jagersma
2020-03-20 14:04 ` [PATCH 0/3] coff-go32-exe: support variable-length stubs Nick Clifton
2020-03-20 15:38 ` J.W. Jagersma
2020-03-20 19:42 ` DJ Delorie
2020-03-21 16:07 ` J.W. Jagersma
2020-04-01 16:45 ` J.W. Jagersma [this message]
2020-03-25 17:54 ` [PATCH 4/3+] coff-go32-exe: avoid reallocating stub on copy J.W. Jagersma
2020-04-02 13:34 ` [PATCH 0/3] coff-go32-exe: support variable-length stubs Nick Clifton
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=0eebb21e-11b1-c267-0782-0ebc8d5af346@gmail.com \
--to=jwjagersma@gmail.com \
--cc=binutils@sourceware.org \
--cc=dj@delorie.com \
--cc=nickc@redhat.com \
--cc=stsp@users.sourceforge.net \
/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).