From: Patrick Lauer <patrick@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Bug #565566: Why is it still not fixed?
Date: Tue, 23 Feb 2016 22:54:48 +0100 [thread overview]
Message-ID: <56CCD528.20903@gentoo.org> (raw)
In-Reply-To: <20160223194646.3ada41c0@gentoo.org>
On 02/23/2016 07:46 PM, Alexis Ballier wrote:
> On Tue, 23 Feb 2016 18:14:36 +0100
> Patrick Lauer <patrick@gentoo.org> wrote:
>
>> See https://bugs.gentoo.org/show_bug.cgi?id=565566
>>
>> Since we have ChangeLogs again (November) they've been in backwards
>> order. Which is not really good - it breaks tools (like emerge
>> --changelog) and makes it harder to read for humans.
>>
>> As a bonus it's inconsistent because the old Changelog-2015 files are
>> in normal order, and the new ones are reversed. Which sense no makes.
>>
>> The suggestions in the bug are of great entertainment value, but they
>> all avoid the simple idea of generating ChangeLogs in changelog
>> (reverse chronological) order. Which would fix all tools and make
>> almost every consumer of changelogs happy.
>>
>> So, can we please, after over 4 months of stalling, just fix this
>> embarassment?
>>
> As much as I agree with you there, please use proper communication
> channels and avoid spamming -dev list for single issues.
>
Proper communication channels have failed for 3+ months, maybe putting a
spotlight on things gets things moving.
User-visible breakage for half a year is just insane, I have no idea why
this is "impossible to fix".
Maybe people have gotten used to things being clunky and
not-really-working, I don't get used to it and will rub capsaicin in the
wounds until situation improves.
prev parent reply other threads:[~2016-02-23 21:55 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 17:14 [gentoo-dev] Bug #565566: Why is it still not fixed? Patrick Lauer
2016-02-23 18:07 ` Alec Warner
2016-02-23 21:53 ` Patrick Lauer
2016-02-24 0:33 ` [gentoo-dev] " Duncan
2016-02-24 0:50 ` Kristian Fiskerstrand
2016-02-24 2:53 ` Rich Freeman
2016-02-24 4:24 ` Duncan
2016-02-24 5:49 ` Kent Fredric
2016-02-24 7:29 ` Duncan
2016-02-24 10:35 ` Kent Fredric
2016-02-24 19:18 ` Raymond Jennings
2016-02-24 20:16 ` Luis Ressel
2016-02-24 21:15 ` Daniel Campbell
2016-02-24 22:16 ` Brian Dolbec
2016-02-25 7:12 ` Martin Vaeth
2016-02-25 23:12 ` Gordon Pettey
2016-02-26 11:00 ` Martin Vaeth
2016-02-26 11:11 ` Rich Freeman
2016-02-26 12:59 ` Martin Vaeth
2016-02-26 13:37 ` Rich Freeman
2016-02-27 10:30 ` Martin Vaeth
2016-02-25 5:03 ` Duncan
2016-02-25 5:46 ` Kent Fredric
2016-02-25 8:02 ` Consus
2016-02-25 8:59 ` Kent Fredric
2016-02-25 10:48 ` M. J. Everitt
2016-02-24 4:38 ` Vadim A. Misbakh-Soloviov
2016-02-24 5:36 ` Duncan
2016-02-24 2:39 ` Rich Freeman
2016-02-27 13:14 ` Luca Barbato
2016-02-27 22:35 ` Raymond Jennings
2016-02-27 22:50 ` Robin H. Johnson
2016-02-27 23:08 ` Patrick Lauer
2016-02-28 8:27 ` Martin Vaeth
2016-02-28 3:28 ` Duncan
2016-02-23 18:46 ` [gentoo-dev] " Alexis Ballier
2016-02-23 21:54 ` Patrick Lauer [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56CCD528.20903@gentoo.org \
--to=patrick@gentoo.org \
--cc=gentoo-dev@lists.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