From: Peter Volkov <pva@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Council May Summary: Changes to ChangeLog handling
Date: Mon, 30 May 2011 16:03:42 +0400 [thread overview]
Message-ID: <1306757022.9216.36.camel@tablet> (raw)
In-Reply-To: <1305886782.17955.29.camel@localhost>
В Птн, 20/05/2011 в 13:19 +0300, Mart Raudsepp пишет:
> On T, 2011-05-17 at 13:32 +0300, Petteri Räty wrote:
> > http://www.gentoo.org/proj/en/council/meeting-logs/20110510-summary.txt
> >
> > Please note that you must now update ChangeLog with each commit. For
> > more information please see the meeting log and the preceding mailing
> > list thread:
> >
> > http://www.gentoo.org/proj/en/council/meeting-logs/20110510.txt
> > http://archives.gentoo.org/gentoo-dev/msg_eaefa325b31360324d0fe53d0b9071e6.xml
So, I just realized that we have to update Changelogs for everything,
whitespaces and comments included. Even after reading meeting logs I
still wonder, why council have decided to vote policy change that was
not supported even by minority of developers? The whole idea after human
editable ChangeLogs was to avoid whitespace changes and changes in
comments. In the current state it is possible to generate them on rsync
servers and avoid this burden.
I would like council to update policy to allow exclude whitespace
changes and changes in comments.
--
Peter.
next prev parent reply other threads:[~2011-05-30 12:05 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 10:32 [gentoo-dev] Council May Summary: Changes to ChangeLog handling Petteri Räty
2011-05-20 10:19 ` Mart Raudsepp
2011-05-30 12:03 ` Peter Volkov [this message]
2011-05-30 12:23 ` Ulrich Mueller
2011-05-30 18:07 ` William Hubbs
2011-05-30 17:52 ` Michał Górny
2011-05-30 21:55 ` Brian Harring
2011-05-30 22:05 ` Common sense in [gentoo-dev] (was Council May Summary: Changes to ChangeLog handling) Andreas K. Huettel
2011-05-30 22:14 ` [gentoo-dev] Re: Common sense in " Diego Elio Pettenò
2011-05-30 23:38 ` Common sense in [gentoo-dev] " Brian Harring
2011-05-31 0:01 ` Ângelo Arrifano
2011-06-01 15:08 ` RFC: better policy for ChageLogs (was: Re: [gentoo-dev] " Peter Volkov
2011-06-01 15:15 ` [gentoo-dev] Re: RFC: better policy for ChageLogs Markos Chandras
2011-06-01 15:27 ` Samuli Suominen
2011-06-01 15:34 ` Ciaran McCreesh
2011-06-02 11:21 ` Jorge Manuel B. S. Vicetto
2011-06-01 15:39 ` Andreas K. Huettel
[not found] ` <BANLkTimgHYKnfbeQJpq829YBeE-5Yz=aEg@mail.gmail.com>
2011-06-01 16:24 ` Andreas K. Huettel
2011-06-01 19:50 ` Nirbheek Chauhan
2011-06-01 23:29 ` Jorge Manuel B. S. Vicetto
2011-06-01 23:37 ` Matt Turner
2011-06-02 5:09 ` Peter Volkov
2011-06-02 7:29 ` Duncan
2011-06-02 7:40 ` Eray Aslan
2011-06-02 11:20 ` Patrick Lauer
2011-06-02 11:05 ` Nirbheek Chauhan
2011-06-02 11:10 ` Ciaran McCreesh
2011-06-02 14:43 ` Rich Freeman
2011-06-01 15:30 ` Nathan Phillip Brink
2011-06-01 16:44 ` Duncan
2011-06-01 22:59 ` Rich Freeman
2011-06-01 23:21 ` [gentoo-dev] " Diego Elio Pettenò
2011-06-01 23:29 ` [gentoo-dev] " Dale
2011-06-01 23:40 ` Jorge Manuel B. S. Vicetto
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=1306757022.9216.36.camel@tablet \
--to=pva@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