From: Nicholas Wourms <dragon@gentoo.org>
To: Aron Griffis <agriffis@gentoo.org>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] updated gentoolkit with echangelog modification
Date: Sun, 27 Apr 2003 18:12:36 -0400 [thread overview]
Message-ID: <3EAC55D4.1090607@gentoo.org> (raw)
In-Reply-To: 20030427194445.GA23564@time
Aron Griffis wrote:
> I just updated gentoolkit to version 0.1.21. This version includes two
> changes:
>
> 1. echangelog now follows the older, sanctioned format for the
> ChangeLog. This means that all new entries are added at the top. A
> new version or revision will cause a new *version string.
I don't think this is appropriate for -dev, but since you
started it here, I'm going to comment. Why are you doing
this? Sanctioned or not, the "old" way was never enforced,
and not clearly stated as policy in the developer's
handbook. Also, many prefer the new way. Let's consider this:
Old Way:
Changes were spread all willy-nilly over the Changelog in
chronological order. There was no organization other then
that, so it was often difficult to isolate which specific
revision was changed at a glance and when. This, obviously,
doesn't scale well when we start getting changelogs with
100+ entries
New Way:
Changes are still in chronological order, but they are
indexed under each specific ebuild preceded by the star.
that means, if I want to know what's changed to what
version, I can quickly scan the *'ed entries for the
revision I want and there you go. As for finding out
overall what's changed in the last few days, that is also
just as easy as before. I'd merely scan the the top portion
of each revision. This method scales much better and keeps
Changelog entries neat and orderly, even when faced with
100+ entries.
So, for the time being, can we put echangelog back to the
way it was until this is further discussed?
Comments welcomed.
Cheers,
Nicholas
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-04-27 22:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-27 19:44 [gentoo-dev] updated gentoolkit with echangelog modification Aron Griffis
2003-04-27 22:12 ` Nicholas Wourms [this message]
2003-04-27 22:43 ` Aron Griffis
2003-04-28 0:22 ` Daniel Armyr
2003-04-28 13:29 ` Nicholas Wourms
2003-04-28 16:01 ` Daniel Armyr
2003-04-28 20:06 ` Martin Schlemmer
2003-04-28 23:27 ` Evan Powers
2003-04-28 7:52 ` Evan Powers
2003-04-28 10:12 ` Paul de Vrieze
2003-04-28 11:31 ` Aron Griffis
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=3EAC55D4.1090607@gentoo.org \
--to=dragon@gentoo.org \
--cc=agriffis@gentoo.org \
--cc=gentoo-dev@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