From: Alexis Ballier <aballier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: axs@gentoo.org
Subject: Re: [gentoo-dev] On the usefulness of eclass changelog
Date: Wed, 31 Oct 2012 12:39:33 -0300 [thread overview]
Message-ID: <20121031123933.2f690239@gentoo.org> (raw)
In-Reply-To: <5091454D.7060701@gentoo.org>
On Wed, 31 Oct 2012 11:35:41 -0400
Ian Stakenvicius <axs@gentoo.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> On 31/10/12 11:26 AM, Alexis Ballier wrote:
> > On Tue, 30 Oct 2012 18:39:44 -0600 Ryan Hill
> > <dirtyepic@gentoo.org> wrote: [...]
> >>> The file is pointless if not everyone is using it. I've
> >>> offered to remove the file before, and I'm reoffering to do so
> >>> now.
> >>
> >> It's pointy enough for most uses. Let's keep it that way.
> >
> > I would like to know what are those uses. Here are my thoughts
> > about changelogs:
> >
> > We have cvs logs, cvsweb, etc. So what is the value added from
> > changelogs? Well, those logs are per-file as far as I know, and
> > since a new version of a package means a new .ebuild file, keeping
> > track of changes to packages is painful without a changelog which
> > is global to the whole package. Even if we have all the needed
> > information in the cvs log, changelogs for packages are definitely
> > useful. Now for eclasses the situation is different: I want to
> > know what has recently changed in foo.eclass, what is the fastest
> > way? Search through a changelog file with dozens of absolutely
> > unrelated information, or run cvs log/go to sources.gentoo.org ? I
> > tend to do the latter and find eclass changelogs completely
> > useless.
> >
>
> Cool, you do, that's great. This doesn't mean others don't use a
> different process tho, and since it *IS* there and is *SUPPOSED* to be
> filled, and it really doesn't hurt to run 'echangelog "${msg}" && cvs
> ci -m "${msg}"' , why not do it?
so that others are not encouraged to work sub-optimally :)
next prev parent reply other threads:[~2012-10-31 15:40 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20121030190839.A9A3D21600@flycatcher.gentoo.org>
2012-10-30 19:17 ` [gentoo-dev] Re: gentoo-x86/eclass: udev.eclass Fabian Groffen
2012-10-30 19:31 ` Samuli Suominen
2012-10-30 19:49 ` Samuli Suominen
2012-10-30 20:47 ` Doug Goldstein
2012-10-30 21:16 ` Fabian Groffen
2012-10-30 21:22 ` Samuli Suominen
2012-10-31 7:50 ` Fabian Groffen
2012-10-31 7:51 ` Samuli Suominen
2012-10-31 8:56 ` Fabian Groffen
2012-10-31 16:08 ` Samuli Suominen
2012-10-31 16:21 ` Gilles Dartiguelongue
2012-10-31 16:55 ` Samuli Suominen
2012-10-31 15:04 ` Alexis Ballier
2012-10-31 16:19 ` Samuli Suominen
2012-10-30 22:04 ` Ciaran McCreesh
2012-10-30 21:24 ` Michał Górny
2012-10-30 21:28 ` Samuli Suominen
2012-10-31 0:39 ` Ryan Hill
2012-10-31 15:26 ` [gentoo-dev] On the usefulness of eclass changelog Alexis Ballier
2012-10-31 15:35 ` Ian Stakenvicius
2012-10-31 15:39 ` Alexis Ballier [this message]
2012-10-31 16:15 ` Samuli Suominen
2012-10-31 16:26 ` Ian Stakenvicius
2012-10-31 16:38 ` Alexis Ballier
2012-10-31 16:45 ` Jeroen Roovers
2012-10-31 18:17 ` Rich Freeman
2012-10-31 18:33 ` Samuli Suominen
2012-10-30 19:56 ` [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in eclass: udev.eclass Alexis Ballier
2012-10-30 19:57 ` Samuli Suominen
2012-10-30 20:08 ` Alexis Ballier
2012-10-30 20:18 ` Michał Górny
2012-10-30 20:19 ` Samuli Suominen
2012-10-31 14:57 ` Alexis Ballier
2012-10-31 15:09 ` Michał Górny
2012-10-31 15:36 ` Samuli Suominen
2012-10-31 19:17 ` Markos Chandras
2012-10-30 20:06 ` Fabian Groffen
2012-10-30 20:06 ` Ian Stakenvicius
2012-10-30 20:08 ` Samuli Suominen
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=20121031123933.2f690239@gentoo.org \
--to=aballier@gentoo.org \
--cc=axs@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