Re: Copyright on wildmatch.c

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I'm not sure on how i would rewrite hex.c it is just an array.

>From git-compat-util.h i only needed a subset of the file (Lines 699
to 785), as you assumed, but rewriting it also seems pointless as it
is only a few defines and 4 very short functions.

I have asked everybody who changed anything in those lines for their
approval. I hope they all agree.

On Tue, Feb 24, 2015 at 10:46 AM, Duy Nguyen <pclouds@xxxxxxxxx> wrote:
> On Tue, Feb 24, 2015 at 4:29 PM, Guilherme <guibufolo@xxxxxxxxx> wrote:
>> That discussion seems to have just died off.
>>
>> Whom should i write to about making the license change effective? You
>> (Duy Nguyen) seemed to be fine with the license change. Can you, or
>> anyone else, further guide me on the process on making sure i can use
>> the file(s) in TSS?
>
> I'm not a lawyer, but I think after you double check
>
>  - what Jonathan Neider wrote about GPLv3 and Apache2 is true
>  - perhaps check with Anthony Ramine, who is the only person besides
> me that has made changes in wildmatch.c, in b79c0c3 (wildmatch:
> properly fold case everywhere - 2013-05-30)
>
> then wildmatch.c is good for reuse. You probably need to check with
> other people who made changes in hex.c and git-compat-util.h.
> git-shortlog and git-blame could be used to get the email list of
> these people. But maybe it's just easier to rewrite those, hex.c is
> not big and I suspect you don't need much of git-compat-util.h.
> --
> Duy
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]