From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 120629 invoked by alias); 5 Oct 2017 13:43:34 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 120616 invoked by uid 89); 5 Oct 2017 13:43:33 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM,SPF_PASS autolearn=no version=3.3.2 spammy=contribution X-HELO: mail-qt0-f171.google.com X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=RYByxpRXQg9iDgfS8MbyNJPSez+uVKu8eDKRmG1mrEE=; b=lNt/lX+jeIOA0chx4+sp8v2bME0kin3QxZai7P9CDu83lkDOCNuVRyVdxb0Nt2yRRX BMP7g8Q3LAnXybvRI/iRWuAZo1OWLoMZvwaP3f3678QtmddZ5mMkeDKMspGuF8LR8RAZ 2HOsQefcXlbuxv9yw6eHaLSujia7PoffOlJ/islsoRFU1yojFtYyDnh4dOhGkC+Aex+D MSYkj/RjMdcuEHvENB06UeUcLY5ZxhaJ9hTKvuXM6uPNaSMrx9AOvYT/db213wXGrcxO VneJ21ANbInZuUHDP1A9WeaRlXK1UDJJ0Z5CFAW9WcuiSB+qwnoiz3c1SR94/7jVPglc D8oA== X-Gm-Message-State: AMCzsaVslEgtbmp+GCeApDwEQojv+wUv58fsWyEe8N88UZppa1+0UzHM 26KB5vQ9gdNZ2cemBAF/txuNU8fvx70= X-Google-Smtp-Source: AOwi7QAJbJdVV6nULeqIh+KiiLeXx1rp18onpPI8nklSfgcGRM2y9RvJyO61gbS4L1grkogzbwrAIQ== X-Received: by 10.237.53.212 with SMTP id d20mr14600007qte.10.1507211009883; Thu, 05 Oct 2017 06:43:29 -0700 (PDT) Subject: Re: [RFC][PATCH] Refactoring FORTIFY To: George Burgess IV , Joseph Myers Cc: libc-alpha@sourceware.org References: <9ea2b3d3-c7d0-1d36-db4d-4de7b21067f1@linaro.org> From: Adhemerval Zanella Message-ID: <1e61b1be-d7c3-4a44-5aa9-b8176fa4e7b8@linaro.org> Date: Thu, 05 Oct 2017 13:43:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2017-10/txt/msg00248.txt.bz2 I am not sure if Google has an assignment that cover submission of all its engineers. Also, I am not well versed in the requirements for the FSF copyright assignment, the only point I have is the GLIBC wiki entry [1]. Joseph, is the wiki updated with latest guidelines and and does Google current CLA already cover George work? [1] https://sourceware.org/glibc/wiki/Contribution%20checklist#FSF_copyright_Assignment On 03/10/2017 17:53, George Burgess IV wrote: > 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 > 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).