From: Torvald Riegel <triegel@redhat.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: Florian Weimer <fweimer@redhat.com>,
Joseph Myers <joseph@codesourcery.com>,
libc-alpha@sourceware.org
Subject: Re: Update copyright dates not handled by scripts/update-copyrights [committed]
Date: Mon, 02 Jan 2017 16:08:27 +0100 [thread overview]
Message-ID: <1483369707.13143.80.camel@redhat.com> (raw)
In-Reply-To: <20170101095738.GH16617@vapier>
On Sun, 2017-01-01 at 04:57 -0500, Mike Frysinger wrote:
> even better: let's delete them and be done.
Yes, please.
The last discussion of this that I saw was in August 2015. When Mike
proposed to get rid of Changelogs back then, there weren't any reasons
given in response why we would still need to maintain them (sorry if I
missed any); only Andreas mentioned that a tarball release wouldn't have
them.
To me personally, Changelogs are write-only data -- meaning they have no
value for me, and are just overhead. It's not a challenging task for
sure, but you have to pay attention to not make little stupid mistakes,
and I find myself just writing short information there like
* file (function): Adapt.
I'd much rather see us putting all the time required for the changelog
into actually improving the commit message (ie, the reasons for applying
the patch).
Can we please again compare the time we spend on maintaining changelogs
against the time we potentially gain for ... well, something that hasn't
been mentioned in the 2015 discussion? I suspect the effort spent is
much bigger than the gain.
next prev parent reply other threads:[~2017-01-02 15:08 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 [this message]
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
-- 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=1483369707.13143.80.camel@redhat.com \
--to=triegel@redhat.com \
--cc=fweimer@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=vapier@gentoo.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).