From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <libc-alpha-return-85320-listarch-libc-alpha=sources.redhat.com@sourceware.org>
Received: (qmail 13292 invoked by alias); 3 Oct 2017 20:54:31 -0000
Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <libc-alpha.sourceware.org>
List-Subscribe: <mailto:libc-alpha-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/libc-alpha/>
List-Post: <mailto:libc-alpha@sourceware.org>
List-Help: <mailto:libc-alpha-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: libc-alpha-owner@sourceware.org
Received: (qmail 13275 invoked by uid 89); 3 Oct 2017 20:54:31 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-2.7 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM,SPF_PASS autolearn=no version=3.3.2 spammy=
X-HELO: mail-pf0-f180.google.com
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:in-reply-to:references:from:date
         :message-id:subject:to:cc;
        bh=gvzYr3jOxuY8wZm+wdx8M53lVtxpUbNcS9NgjMsYoZo=;
        b=hX4YcYYPdvB96G4Ameumu+74zVldJvBELk2H8UGE+9zhGAOpWqVIDmQRGy5kS4JLJm
         Thgk6ve/BH4T/6TjQos3mLj6oXc0AzWss6iOYyUOD99pfX6vJskFwywfM71vfgl882kA
         QPgqxq+3CBsjDzqUuU3D3SAi/NccTXEEMqVRTm3lbdN7/0gfc2C0bU1450/UvZQSts+M
         b3ZkcVWeNA2+DWeMmbXgQHjx9MPrIkWZMMiz9mohg74qJSqvALahFaX8JhlbM9d5YI3F
         Nd+0AC5l/DXmHqujIO3egGSbE7TJTwqNU/lMNfDwDYCv3c0EOHPQA2dwlMoAh6KnudLd
         cdzA==
X-Gm-Message-State: AMCzsaU97m5bY3U3Ze/6Bhtcrh5adP89zcrA2Cqv3IWg3d9d4inSmNXz
	540vPgs3SM5E7d9D3vgXFKsp2e+6PQAhv4oPqxK6dWKD
X-Google-Smtp-Source: AOwi7QDDJyMBWsurIPRLGZnmC4V1956M905kYyOdDqKy9+AE9raS7PE65Wl7vdq1eZ1JAxZDgCUaNOXYU9+aH06B4Ag=
X-Received: by 10.98.109.69 with SMTP id i66mr5725006pfc.200.1507064068213;
 Tue, 03 Oct 2017 13:54:28 -0700 (PDT)
MIME-Version: 1.0
In-Reply-To: <9ea2b3d3-c7d0-1d36-db4d-4de7b21067f1@linaro.org>
References: <CAKh6zBFAGomCFc+Y9=qpH-2N6AonKUja1R+cWy=p_=T=rs29cQ@mail.gmail.com>
 <9ea2b3d3-c7d0-1d36-db4d-4de7b21067f1@linaro.org>
From: George Burgess IV <george.burgess.iv@gmail.com>
Date: Tue, 03 Oct 2017 20:54:00 -0000
Message-ID: <CAKh6zBFD=7itKYpytb70a1jbi2gd0-tznqj6eagQHMUHb_f1Fg@mail.gmail.com>
Subject: Re: [RFC][PATCH] Refactoring FORTIFY
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: libc-alpha@sourceware.org
Content-Type: text/plain; charset="UTF-8"
X-SW-Source: 2017-10/txt/msg00132.txt.bz2

I have not signed a copyright assignment yet, though I'm more than
happy to do so. Would
http://git.savannah.gnu.org/cgit/gnulib.git/plain/doc/Copyright/request-assign.future
be the appropriate form for me to fill out and send in?

If it changes things, I wrote this as a part of my work with Google,
who says they have a CLA on file with the FSF.

Thank you,
George

On Tue, Oct 3, 2017 at 12:34 PM, Adhemerval Zanella
<adhemerval.zanella@linaro.org> wrote:
> On 11/09/2017 03:26, George Burgess IV wrote:
>> Hello,
>>
>> Attached is a patch that aims to substantially improve FORTIFY's
>> usefulness with clang, and make defining FORTIFY'ed functions require
>> less ceremony.
>
> Due the patch size and complexity and no indication on the message, it
> would be good to know if you already have a copyright assignment, and
> if your work is covered by it.
>
> You will need it to sort this out first so someone can actually look
> into your patch (which I am interested in review btw).