From: liqingqing <liqingqing3@huawei.com>
To: Carlos O'Donell <carlos@redhat.com>,
Liusirui <liusirui@huawei.com>, <libc-alpha@sourceware.org>
Cc: <siddhesh@gotplt.org>, <dj@redhat.com>, <hushiyuan@huawei.com>
Subject: Re: [PATCH] malloc: fix compile error
Date: Fri, 1 Nov 2019 15:47:53 +0800 [thread overview]
Message-ID: <a4633006-cf7d-d80d-c5c7-b3cae115c19a@huawei.com> (raw)
In-Reply-To: <37c6b55d-dac9-f310-5280-7d5216a81b18@huawei.com>
ping again
On 2019/10/31 11:44, liqingqing wrote:
>>> I think you can give more details about the error like the compile
>>> step. and so that the other guys may get more information.
>>>
>>
>> Agreed. The commit message should say which error and which compiler
>> version generated the error.
>>
>> We still can't accept patches from Huawei yet because copyright
>> assignment
>> has not been completed. But thanks for the review!
>>
>
> hello Carlos, how are you?
> we found that other people which is from Huawei also have the same
> problem. below is the discussion.
> https://sourceware.org/ml/libc-alpha/2019-10/msg00905.html
>
> we checked the contribution checklist again, and we also have the same
> question: even if we just fix a bug in the situation that we has already
> completed an fsp copyright assignment, the code also can not be
> accepted? what we need to do next? we expect your or others more
> helps, thank you.
>
hello carlos, I checked the contribution checklist again and i think
maybe it has two different situations. the FSF copy assignment section
said that only "legally signification" required copyright assigment.
here is the copy:
"The Free Software Foundation (holder of the glibc copyrights) requires
copyright assignment for all legally significant changes by a particular
author (read not a company). This webpage describes the copyright
assignment requirements."
and the legally signification changes is defined like that:
http://www.gnu.org/prep/maintain/maintain.html#Legally-Significant
section 6.2 Legally Significant Changes :
"If a person contributes more than around 15 lines of code and/or text
that is legally significant for copyright purposes, we need copyright
papers for that contribution, as described above.
A change of just a few lines (less than 15 or so) is not legally
significant for copyright. A regular series of repeated changes, such as
renaming a symbol, is not legally significant even if the symbol has to
be renamed in many places. Keep in mind, however, that a series of minor
changes by the same person can add up to a significant contribution.
What counts is the total contribution of the person; it is irrelevant
which parts of it were contributed when."
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?
can you give me more suggestions? thank you.
liqingqing
next prev parent reply other threads:[~2019-11-01 7:48 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 [this message]
2019-11-01 12:49 ` Carlos O'Donell
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=a4633006-cf7d-d80d-c5c7-b3cae115c19a@huawei.com \
--to=liqingqing3@huawei.com \
--cc=carlos@redhat.com \
--cc=dj@redhat.com \
--cc=hushiyuan@huawei.com \
--cc=libc-alpha@sourceware.org \
--cc=liusirui@huawei.com \
--cc=siddhesh@gotplt.org \
/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).