This is the mail archive of the mailing list for the glibc project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [RFC PATCH 0/3] bugfix for aarch64 ILP32

On 03/19/2015 12:19 AM, Bamvor Jian Zhang wrote:
> On 2015/3/19 0:08, Carlos O'Donell wrote:
>> On 03/18/2015 06:30 AM, Zhang Jian(Bamvor) wrote:
>>> This is bamvor from Huawei OS team. We test ILP32 support through
>>> LTP testcases for both little endian and big endian. There are some
>>> failures we thought they should be fixed in glibc level, so, here they are.
>> Your changes are legally significant, and will require copyright assignment
>> from Huawei. Are you working on getting copyright assignment? I don't presently
>> see Huawei assignments for glibc (but I do see them for gcc).
>> Please review the contribution checklist:
> Hi, Carlos
> I do not know the exactly status about this assignment, and I try to collect
> the status in huawei. Meanwhile I read the link above. It say "A change of
> just a few lines (less than 15 or so) is not legally significant for
> copyright." Our patch may be less 15 line because of the second may be
> useless according to H,J Lu's suggestion.
> Meanwhile, I found that there is not s-o-b in glibc git commit. Should we
> remove the s-o-b in my patches as well?

If your total contributions is below say ~15 lines [1], then we can accept
it *for* *today*, but if you continue to contribute the number of lines
changed is cumulative by author. Please pursue the appropriate path forward
to get copyright assignment, that way we can just accept any patch you post
regardless of length.

Thank you for contributing :-)



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]