public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jason Stubbs <jstubbs@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 21:37:10 +0900	[thread overview]
Message-ID: <200511072137.10975.jstubbs@gentoo.org> (raw)
In-Reply-To: <200511071111.45798.pauldv@gentoo.org>

On Monday 07 November 2005 19:11, Paul de Vrieze wrote:
> On Saturday 05 November 2005 06:34, Alec Warner wrote:
> > emerge --changelog has no 'official' format.  I believe echangelog
> > actually puts the changes in the correct format for emerge -l to read,
> > however not everyone uses echangelog.  Many developers commit in an
> > incompatable syntax causing the parsing to fail.  This I believe, is an
> > implementation issue.  Obviously if someone is trying to get an upgrade
> > guide to users they aren't going to commit in an incompatable format.
>
> I would also like to add that the changelog has too much information to be
> usefull as a news source. In all honesty, when I'm emerging a new version
> of a package I'm not interested in keyword bumps, small cosmetic changes,
> added auxiliary scripts or documentation. These are all documented (and
> should be) in the changelog. If I update my system however, I'm mainly
> interested in knowing whether something is going to break. News would be
> a way to provide this knowledge to a user in an as concise as possible
> way.

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 ;)

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.

--
Jason Stubbs
-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2005-11-07 12:38 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 [this message]
2005-11-07 16:06                             ` Grant Goodyear
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=200511072137.10975.jstubbs@gentoo.org \
    --to=jstubbs@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