public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: 黄莺 <ying.huang@oss.cipunited.com>
To: "Florian Weimer" <fweimer@redhat.com>
Cc: libc-alpha <libc-alpha@sourceware.org>,
	苏运强 <yunqiang.su@oss.cipunited.com>
Subject: Re: [PATCH v2] MIPS: Sync elf.h from binutils
Date: Thu, 01 Jun 2023 18:46:59 +0800	[thread overview]
Message-ID: <114fe517229b8cc0e504238f0d8553dd3528f5e9.4ee67b39.de37.4ed8.9e61.cfd0dfef86ef@feishu.cn> (raw)
In-Reply-To: <87v8g7scap.fsf@oldenburg.str.redhat.com>

[-- Attachment #1: Type: text/plain, Size: 473 bytes --]

Yes, the entire company signed the fsf copyright assignment.
Thanks,
Ying
> From:"Florian Weimer"<fweimer@redhat.com>
> Date:Thu, Jun 1, 18:32
> Subject:Re: [PATCH v2] MIPS: Sync elf.h from binutils
> To:"Ying Huang"<ying.huang@oss.cipunited.com>
> Cc:<libc-alpha@sourceware.org>,<yunqiang.su@oss.cipunited.com>
> * Ying Huang:
> 
> > Could you help commit PATCH v2? 
> 
> Is this contribution covered by an FSF copyright assignment?
> 
> Thanks,
> Florian

  reply	other threads:[~2023-06-01 10:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-16  9:12 Ying Huang
2023-06-01  9:17 ` [PATCH " Ying Huang
2023-06-01  9:21   ` Florian Weimer
2023-06-01  9:40     ` Ying Huang
2023-06-01 10:32       ` Florian Weimer
2023-06-01 10:46         ` 黄莺 [this message]
2023-06-28  1:43         ` Ying Huang
  -- strict thread matches above, loose matches on Subject: below --
2023-05-16  6:15 Ying Huang
2023-05-16  6:53 ` Florian Weimer
2023-05-19 11:21   ` Maciej W. Rozycki
2023-05-19 12:43     ` Gabriel Ravier

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=114fe517229b8cc0e504238f0d8553dd3528f5e9.4ee67b39.de37.4ed8.9e61.cfd0dfef86ef@feishu.cn \
    --to=ying.huang@oss.cipunited.com \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=yunqiang.su@oss.cipunited.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).