From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qv1-xf31.google.com (mail-qv1-xf31.google.com [IPv6:2607:f8b0:4864:20::f31]) by sourceware.org (Postfix) with ESMTPS id AD1953857C4C for ; Mon, 23 Nov 2020 20:13:23 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org AD1953857C4C Received: by mail-qv1-xf31.google.com with SMTP id 9so5254111qvk.9 for ; Mon, 23 Nov 2020 12:13:23 -0800 (PST) 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=G0t8iWy1unXMV9vMsPXxQoF1AOxK/7gFmO+Eu0akOJA=; b=Xe41hSorBMMbVDoFXyt5JFMvZLGlc8ZXNgSn44cr/3Trf3uGw0Ft5CmvMnFR0+m1ao IzvptFyPS550qmfdrHefi+H0JrhGcm4+hbT1GIVRma1HSoWG3H5R6jW5jDM09n+51Rh0 seoOou2EH/uqN8T+3pjJlR4sPqmjD7QwaEqfS6Zrr71ja8HydRE6QhwIw5Zv5yEIEVqJ eiNLfbkMUbi6G5fhHKM17wxLFJE/Yr8E5MypXIyRyQ7jTjHIJed6WcDnwI3Veix9LH4e 8RiPJpuaBgxrklYmtJ17YXmvhjN20/L1U5X0aWNcEgfW3zLom5XhBDT+rli7T3DVTqk7 UE6A== X-Gm-Message-State: AOAM532/2NfZdWZm1cA74Cuo7r6b8ZwIcIuiMtUxG+Ax1kuyMJDBGSKY DPG4DCdSErMrn494VbpZttJZiIDt/fk= X-Google-Smtp-Source: ABdhPJzj7K8bVYvcIm9X05EkwTGQxMgBG4TA9fT2uDbFRLXHHb1jqRzDHGllyfiy/vV9vGOjJ1itnw== X-Received: by 2002:a05:6214:6a2:: with SMTP id s2mr1158249qvz.58.1606162403047; Mon, 23 Nov 2020 12:13:23 -0800 (PST) Received: from [192.168.0.41] (75-166-106-198.hlrn.qwest.net. [75.166.106.198]) by smtp.gmail.com with ESMTPSA id r48sm4903867qtr.21.2020.11.23.12.13.22 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 23 Nov 2020 12:13:22 -0800 (PST) Subject: Re: broken check: You should edit tm.texi.in rather than tm.texi To: Joseph Myers Cc: =?UTF-8?Q?Martin_Li=c5=a1ka?= , GCC Development References: From: Martin Sebor Message-ID: <7b8dd4da-b93f-c303-c07e-c97e55695b43@gmail.com> Date: Mon, 23 Nov 2020 13:13:21 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, NICE_REPLY_A, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: gcc@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Nov 2020 20:13:25 -0000 On 11/23/20 12:45 PM, Joseph Myers wrote: > On Mon, 23 Nov 2020, Martin Sebor via Gcc wrote: > >> I never did understand what it was complaining about, or the point >> of making us jump through these hoops for updates to the internals >> manual when the (arguably far more impactful) changes to GCC source >> code or the user-visible manual aren't subject to the same check. > > The point of this check is that the FSF was unable to come up with a dual > licensing notice allowing a single source file with content explicitly > dual-licensed under the GPL and GFDL, so instead both GPL and GFDL copies > of that content (doc strings for target hooks) need to be checked into the > repository, and the check makes sure that the two copies are in sync. The > person contributing such documentation should commit it with both copies > in sync to ensure it's properly available under both licenses. Otherwise, > e.g. moving existing internals manual text documenting a target macro into > such a doc string for a target hook and so making it available under a new > license, a global reviewer or docstring relicensing maintainer can approve > the move. I'd expect the best way to ensure the two copies of the contributed text are in sync is to copy it automatically. If the only point of asking the author to do it by hand each time they change the file is to "Verify that they have permission to grant a GFDL license" than that step could be done once, the result recorded somewhere (e.g., in the MAINTAINERS file), and automated when making changes by having the script look it up. Is making this change feasible? Martin