From: Joseph Myers <joseph@codesourcery.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Florian Weimer <fweimer@redhat.com>, <libc-alpha@sourceware.org>
Subject: Re: Update copyright dates not handled by scripts/update-copyrights [committed]
Date: Mon, 2 Jan 2017 17:22:34 +0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1701021720080.24470@digraph.polyomino.org.uk> (raw)
In-Reply-To: <d3d876ee-9c34-6eb9-68ce-4ce50050326a@cs.ucla.edu>
On Mon, 2 Jan 2017, Paul Eggert wrote:
> Unfortunately there's a problem with this approach: it's a pain to merge. This
> is because different branches can have different committed ChangeLog files,
> which are mostly autogenerated but contain some hand edits. The autogenerated
Since in practice we don't do point releases from branches in glibc, with
my proposal (absent persuading the GCS maintainers of the non-utility for
ChangeLogs in certain cases) ChangeLogs would most likely only ever be
updated on master, not on branches. Branches would have commit messages
following the relevant conventions, but the script probably wouldn't be
run there.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2017-01-02 17:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-01 0:27 Update copyright dates not handled by scripts/update-copyrights [committed] Joseph Myers
2017-01-01 7:22 ` Florian Weimer
2017-01-01 9:57 ` Mike Frysinger
2017-01-02 15:08 ` Torvald Riegel
2017-01-02 15:23 ` Joseph Myers
2017-01-02 15:42 ` Torvald Riegel
2017-01-02 17:19 ` Joseph Myers
2017-01-02 17:27 ` Joseph Myers
2017-01-02 18:03 ` Torvald Riegel
2017-01-02 17:55 ` Torvald Riegel
2017-01-02 18:01 ` Joseph Myers
2017-01-02 18:03 ` Torvald Riegel
2017-01-02 13:45 ` Joseph Myers
2017-01-02 13:55 ` Florian Weimer
2017-01-02 14:00 ` Joseph Myers
2017-01-02 15:50 ` Paul Eggert
2017-01-02 17:22 ` Joseph Myers [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-01-01 0:22 Joseph Myers
2019-01-01 0:16 Joseph Myers
2018-01-01 0:41 Joseph Myers
2016-01-04 16:27 Joseph Myers
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.20.1701021720080.24470@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=eggert@cs.ucla.edu \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).