From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Joseph Myers Newsgroups: gmane.comp.lib.glibc.alpha Subject: Re: Update copyright dates not handled by scripts/update-copyrights [committed] Date: Mon, 2 Jan 2017 13:45:37 +0000 Message-ID: References: <0d577e78-86dc-5c4d-7afc-f4ff6e3a5eb9@redhat.com> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-Trace: blaine.gmane.org 1483364772 9108 195.159.176.226 (2 Jan 2017 13:46:12 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 2 Jan 2017 13:46:12 +0000 (UTC) User-Agent: Alpine 2.20 (DEB 67 2015-01-07) Cc: To: Florian Weimer Original-X-From: libc-alpha-return-76511-glibc-alpha=m.gmane.org@sourceware.org Mon Jan 02 14:46:08 2017 Return-path: Envelope-to: glibc-alpha@blaine.gmane.org DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:cc:subject:in-reply-to:message-id :references:mime-version:content-type; q=dns; s=default; b=jJ9G8 dcUgeHA1usvjtqoanTYuvfCAHhDPEh1Y5rB1nl7qay70/tuVoRdG7x9wSPom1dEo tYduCdlQlFf+KCnyLD6KAl5lr5qxmkDktTDJikWHmXPVK4BM4xsJAFyvpn9f3THf kgvcGOXGEFnuL3Xsw6AYh8zobOHml3peg1pee4= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:cc:subject:in-reply-to:message-id :references:mime-version:content-type; s=default; bh=RGdYwvUle9N pnzXrmLb3wgJ6S+c=; b=WY9vtNjoLUQe03S7Sa5jX7zd4wK00oIXDd3XnkoTBts wPXS/TLLiOhjXEefIac6XpeZNjIpi11xpPqhnNL/laG+H03UWzLej53ERdEz9s9H dnIZouqRbDyhhEgCbi0uH1umAXz6FOpRfa6h/qKnZxrkIxbM4zcwdClwkzO7bhzU = Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Original-Sender: libc-alpha-owner@sourceware.org Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-HELO: relay1.mentorg.com In-Reply-To: <0d577e78-86dc-5c4d-7afc-f4ff6e3a5eb9@redhat.com> X-ClientProxiedBy: svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1) To svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1) Xref: news.gmane.org gmane.comp.lib.glibc.alpha:68866 Archived-At: Received: from server1.sourceware.org ([209.132.180.131] helo=sourceware.org) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cO2w3-0000m3-4y for glibc-alpha@blaine.gmane.org; Mon, 02 Jan 2017 14:45:59 +0100 Received: (qmail 12709 invoked by alias); 2 Jan 2017 13:45:58 -0000 Received: (qmail 11075 invoked by uid 89); 2 Jan 2017 13:45:58 -0000 On Sun, 1 Jan 2017, Florian Weimer wrote: > On 01/01/2017 01:27 AM, Joseph Myers wrote: > > I've updated copyright dates in glibc for 2017. This is the patch for > > the changes not generated by scripts/update-copyrights and subsequent > > build / regeneration of generated files. > > Could we rotate the ChangeLog file, too, please? ChangeLog rotation was previously objected to in . What I think we should now aim for regarding ChangeLogs - not during a freeze apart maybe from the first step - is: 1. Move libidn/ChangeLog to ChangeLog.libidn, localedata/ChangeLog to ChangeLog.localedata, stop using separate ChangeLogs for those subdirectories and just put everything in the toplevel ChangeLog. 2. Develop conventions for embedding ChangeLog entries in git commit messages to support automatic ChangeLog generation. Develop a script to be run from the pre-receive hook that rejects master and release branch updates unless they have a properly formatted ChangeLog entry following those conventions in their commit messages for each pushed commit (or follow appropriate conventions for indicating a commit that deliberately does not have a ChangeLog entry). Develop a script that updates ChangeLog with the messages for all commits since that script was last run. 3. Declare a flag day, at which ChangeLog is renamed to ChangeLog.18 and future commits do not add entries to ChangeLog except as a result of running that script. 4. As the last commit before a release is tagged, the script would be run to update ChangeLog and the results committed, so that releases can continue to be built with "git archive". In addition, if a mistake or omission in a ChangeLog entry in a past commit message is to be corrected, the approach would be to run the script, commit the results, then edit the resulting ChangeLog content; this avoids the need for any on-the-side list of edits to ChangeLog entries. Not needing to be done as part of the move to automatically generated ChangeLogs, but facilitated by it, would be arranging for patchwork to automatically mark patches committed when the git-patch-id of a commit is the same as that of a patch in patchwork (because it would become normal for a patch posted for review to be the same as the patch that gets committed). This would reduce the extent to which patchwork fills up with patches that have in fact been committed, although manual work is still needed to deal with the backlog (both reviewing patches that need review, and updating entries for patches that have in fact been committed or superseded). -- Joseph S. Myers joseph@codesourcery.com