From: Peter Volkov <pva@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Re: [gentoo-dev] Call for agenda items -- Council meeting 2011-11-08
Date: Mon, 31 Oct 2011 12:27:47 +0400 [thread overview]
Message-ID: <1320049667.17148.37.camel@tablet> (raw)
In-Reply-To: <20111031091445.5b5697a7@pomiocik.lan>
В Пнд, 31/10/2011 в 09:14 +0100, Michał Górny пишет:
> On Mon, 31 Oct 2011 10:43:49 +0400
> Peter Volkov <pva@gentoo.org> wrote:
>
> > В Срд, 26/10/2011 в 18:35 +0200, Michał Górny пишет:
> > > On Wed, 26 Oct 2011 18:30:25 +0200
> > > Fabian Groffen <grobian@gentoo.org> wrote:
> >
> > > > In less than two weeks, the council will meet again. This is the
> > > > time to raise and prepare items that the council should put on
> > > > the agenda to vote on.
> > >
> > > As an extension of ChangeLog topic, I'd like to suggest to require
> > > developers to commit packages with matching (same) ChangeLog entries
> > > and commit messages.
> >
> > I don't see how this logic may work in case you need to modify
> > Changelog, so ... wontfix :)
>
> 'Need' is a very bad word here. I'd rather use 'have a wannabe'.
We have and use this feature now so... better word should be "must"
until somebody provides very valid reasons to drop it. Speaking about
your reasons:
> 1) easier migration to autogenerated ChangeLogs if we want that at
> some point,
Still questionable need.
> 2) better availability of the information (right now, looking up
> changes sometimes involves checking both CVS log and ChangeLog message
> to see what actually happened),
Was discussed many times with the resolution: they should be different.
> 3) one step towards preventing useless ChangeLog entries.
In the spirit of Gentoo to fix this issue we just need to improve our
tools and the first step, moving echangelog into repoman, is already
done:
https://bugs.gentoo.org/show_bug.cgi?id=337853
With best regards,
--
Peter.
next prev parent reply other threads:[~2011-10-31 8:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-26 16:30 [gentoo-project] Call for agenda items -- Council meeting 2011-11-08 Fabian Groffen
2011-10-26 16:35 ` [gentoo-project] Re: [gentoo-dev] " Michał Górny
2011-10-26 16:37 ` Fabian Groffen
2011-10-26 16:49 ` Michał Górny
2011-10-26 17:06 ` Fabian Groffen
2011-10-26 17:11 ` Michał Górny
2011-10-26 17:15 ` Fabian Groffen
[not found] ` <1319652305.5300.7.camel@belkin4>
2011-10-26 19:09 ` Matt Turner
2011-10-26 20:58 ` Fabian Groffen
2011-10-26 21:03 ` Chí-Thanh Christopher Nguyễn
2011-10-26 21:07 ` Fabian Groffen
2011-10-26 22:13 ` Chí-Thanh Christopher Nguyễn
2011-10-27 7:08 ` Fabian Groffen
2011-10-26 16:50 ` Markos Chandras
2011-10-31 6:43 ` Peter Volkov
2011-10-31 8:14 ` Michał Górny
2011-10-31 8:27 ` Peter Volkov [this message]
2011-10-31 9:52 ` [gentoo-project] " Petteri Räty
2011-10-31 10:27 ` Ulrich Mueller
2011-11-01 21:07 ` Petteri Räty
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=1320049667.17148.37.camel@tablet \
--to=pva@gentoo.org \
--cc=gentoo-project@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