From: "J.W. Jagersma" <jwjagersma@gmail.com>
To: DJ Delorie <dj@delorie.com>
Cc: nickc@redhat.com, binutils@sourceware.org, stsp@users.sourceforge.net
Subject: Re: [PATCH 0/3] coff-go32-exe: support variable-length stubs
Date: Sat, 21 Mar 2020 17:07:51 +0100 [thread overview]
Message-ID: <30371c22-d318-7bbe-9928-d6404f19e06a@gmail.com> (raw)
In-Reply-To: <xn7dzen781.fsf@envy.delorie.com>
On 2020-03-20 20:42, DJ Delorie wrote:
> "J.W. Jagersma" <jwjagersma@gmail.com> writes:
>> Will this assignment also cover future submissions to GNU?
>
> They typically do, and you may list more than one project at a time in
> your application (i.e. list binutils and gcc).
The assignment form specifically states that "it will not cover other
unrelated future changes to the same program". I think it would be
convenient if this and the upcoming patches could be covered by one
signature. If that complicates things a lot or if it's not possible
for some other reason, then I'll fill in this form for just the gcc and
binutils patches I've already submitted.
next prev parent reply other threads:[~2020-03-21 16:07 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 [this message]
2020-04-01 16:45 ` J.W. Jagersma
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=30371c22-d318-7bbe-9928-d6404f19e06a@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).