public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox•com>
To: Guilherme <guibufolo@gmail•com>
Cc: Duy Nguyen <pclouds@gmail•com>,
	"git\@vger.kernel.org" <git@vger•kernel.org>
Subject: Re: Copyright on wildmatch.c
Date: Tue, 24 Feb 2015 10:59:39 -0800	[thread overview]
Message-ID: <xmqqzj83qgo4.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CAMDzUtxf0gF=JDgEk9EU3W2VWuP-Qy8-Kz-fTx_Y16UeFRGiYA@mail.gmail.com> (Guilherme's message of "Tue, 24 Feb 2015 13:17:26 +0100")

Guilherme <guibufolo@gmail•com> writes:

> 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 do not think I have any contributions of significance under
copyright protection in the parts of that file.  The ctype-related
lines in git-compat-util.h attribute to me primarily because they
were moved by 4050c0df (Clean up compatibility definitions,
2005-12-05) from what Linus wrote in another file to the present
location.

      parent reply	other threads:[~2015-02-24 18:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAMDzUtyitrK__iE9ykfTuP+Ooq0FwMPp_NVgBfBGbSV52+OPoQ@mail.gmail.com>
2015-02-24  8:08 ` Fwd: Copyright on wildmatch.c Guilherme
2015-02-24  8:58   ` Duy Nguyen
2015-02-24  9:29     ` Guilherme
2015-02-24  9:46       ` Duy Nguyen
2015-02-24 12:17         ` Guilherme
2015-02-24 12:22           ` Guilherme
2015-02-24 12:34             ` Guilherme
2015-02-24 12:54               ` Guilherme
2015-02-24 13:35                 ` Anthony Ramine
2015-02-24 15:58               ` René Scharfe
2015-02-24 22:16               ` Jim Meyering
2015-02-24 18:59           ` Junio C Hamano [this message]

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=xmqqzj83qgo4.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    --cc=guibufolo@gmail$(echo .)com \
    --cc=pclouds@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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