From: Grant Goodyear <g2boojum@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: GLEP 42 (Was: Getting Important Updates To Users)
Date: Mon, 7 Nov 2005 10:06:08 -0600 [thread overview]
Message-ID: <20051107160608.GA9318@bmb24.uth.tmc.edu> (raw)
In-Reply-To: <200511072137.10975.jstubbs@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1922 bytes --]
Jason Stubbs wrote: [Mon Nov 07 2005, 06:37:10AM CST]
> So what's the point of the ChangeLog again? Move load from the CVS
> server and onto the rsync servers? (Don't answer that - just beating a
> dead horse ;)
*Grin* I'm going to answer anyway, since the answer isn't necessarily
obvious to everybody. Once upon a time, the expectation was that the
ChangeLog contained information about package modifications that would
be of interest to users, while the CVS log would contain info mainly of
interest to devs. Of course, that was when viewcvs accessed the live
tree, too. Since then, there seems to have been a consensus that the
CVS log should really be autogenerated from the ChangeLog, which itself
is created using ``echangelog``. My view is that the ChangeLog should
contain user-readable descriptions (although we also encourage some
useful jargon such as "version bump") of every change a package has
undergone, providing a fairly complete history for that package that is
much more readable than iterating through CVS diffs. Consequently, the
ChangeLog has far too much information to realistically serve as a
low-noise news source. (One could imagine tagging certain ChangeLog
entries as being particularly important, but that forces news to be
package based, and seems overly complicated, so please forget that I
ever brought it up.)
> I'm really just against having it in emerge, especially with the current
> suggestion of portage just doing a little bit of maintenance work for
> external tools and nothing else.
I'm not sure exactly what you're arguing here. Is it just that you
think that the news stuff should be a post-sync hook instead of being
triggered explicitly by "emerge"?
-g2boojum-
--
Grant Goodyear
Gentoo Developer
g2boojum@gentoo.org
http://www.gentoo.org/~g2boojum
GPG Fingerprint: D706 9802 1663 DEF5 81B0 9573 A6DC 7152 E0F6 5B76
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-11-07 16:10 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-31 23:36 [gentoo-dev] GLEP 42 (Was: Getting Important Updates To Users) Chris White
2005-10-31 23:41 ` [gentoo-dev] " Dan Meltzer
2005-10-31 23:52 ` Dan Meltzer
2005-11-01 7:56 ` Wernfried Haas
2005-11-01 14:32 ` Chris Gianelloni
2005-11-01 19:32 ` Stuart Herbert
2005-11-01 19:51 ` Chris Gianelloni
2005-11-03 19:40 ` Stuart Herbert
2005-11-04 1:10 ` Nathan L. Adams
2005-11-04 8:22 ` Sami Näätänen
2005-11-04 14:26 ` Xavier Neys
2005-11-04 16:44 ` Jason Stubbs
2005-11-04 18:53 ` Alec Joseph Warner
2005-11-05 5:08 ` Jason Stubbs
2005-11-05 5:34 ` Alec Warner
2005-11-07 10:11 ` Paul de Vrieze
2005-11-07 12:37 ` Jason Stubbs
2005-11-07 16:06 ` Grant Goodyear [this message]
2005-11-07 16:44 ` Jason Stubbs
2005-11-07 16:43 ` Stuart Herbert
2005-11-05 9:58 ` [gentoo-dev] " Duncan
2005-11-05 12:54 ` [gentoo-dev] " Michiel de Bruijne
2005-11-06 19:32 ` R Hill
2005-11-01 19:53 ` Mike Williams
2005-10-31 23:46 ` [gentoo-dev] " Brian Harring
2005-11-01 10:51 ` Jason Stubbs
2005-11-01 0:42 ` Ciaran McCreesh
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=20051107160608.GA9318@bmb24.uth.tmc.edu \
--to=g2boojum@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