From: Carlos O'Donell <carlos@redhat.com>
To: liqingqing <liqingqing3@huawei.com>,
Liusirui <liusirui@huawei.com>,
libc-alpha@sourceware.org, zhangxuelei4@huawei.com
Cc: siddhesh@gotplt.org, dj@redhat.com, hushiyuan@huawei.com
Subject: Re: [PATCH] malloc: fix compile error
Date: Fri, 1 Nov 2019 08:49:12 -0400 [thread overview]
Message-ID: <42bb67c3-91e2-a040-0f64-bcdd33b97cb6@redhat.com> (raw)
In-Reply-To: <a4633006-cf7d-d80d-c5c7-b3cae115c19a@huawei.com>
On 11/1/19 3:47 AM, liqingqing wrote:
> so I think for few changes like a bugfix, the patche can be
> accepted. and for "legally significant changes" , we also need your
> help: what is possible contribute ways? a public huawei account
> which is approved by the supervisor? or an huawei's public copyright
> assignment?
The goal right now is to get a "corporate" assignment in place of Huawei.
It would allow all Huawei employees to submit code to glibc.
Xuelei (on TO:) is already working with the FSF on the corporate assignment.
I would suggest coordinating with Xuelei.
We can not accept code from Huawei employees until the corporate assignment is signed.
My sincerest apologies for the delay.
I look forward to accepting more code from such motivated and dedicated developers!
--
Cheers,
Carlos.
next prev parent reply other threads:[~2019-11-01 12:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-30 6:36 [PATCH] malloc: fix compile error Liusirui
2019-10-30 7:27 ` liqingqing
2019-10-30 11:40 ` Carlos O'Donell
2019-10-31 3:44 ` liqingqing
2019-11-01 7:47 ` liqingqing
2019-11-01 12:49 ` Carlos O'Donell [this message]
2019-10-30 18:39 ` Florian Weimer
-- strict thread matches above, loose matches on Subject: below --
2020-01-13 12:08 liusirui
2020-01-13 12:13 ` liqingqing
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42bb67c3-91e2-a040-0f64-bcdd33b97cb6@redhat.com \
--to=carlos@redhat.com \
--cc=dj@redhat.com \
--cc=hushiyuan@huawei.com \
--cc=libc-alpha@sourceware.org \
--cc=liqingqing3@huawei.com \
--cc=liusirui@huawei.com \
--cc=siddhesh@gotplt.org \
--cc=zhangxuelei4@huawei.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).