From: Samuli Suominen <ssuominen@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Devmanual text on ChangeLogs
Date: Sat, 30 Apr 2011 12:02:35 +0300 [thread overview]
Message-ID: <4DBBD02B.3060909@gentoo.org> (raw)
In-Reply-To: <4DBBCC6D.7080504@gentoo.org>
On 04/30/2011 11:46 AM, Petteri Räty wrote:
> http://devmanual.gentoo.org/ebuild-writing/misc-files/changelog/index.html
>
> There doesn't seem to be a common opinion on what the policy for
> ChangeLog entries is. See:
>
> http://archives.gentoo.org/gentoo-dev/msg_f829da2375f1ceab766a800913cc4998.xml
>
> I propose a simple new text: "Every commit should have an entry in
> ChangeLog." If we eventually autogenerate them from git logs this would
> happen any way (unless some kind of filtering system is in the middle)
> so we could already start now. I think it's better to have more than
> less information available to users.
>
> Regards,
> Petteri
>
"Every new file, and modification to existing file should have an entry
in ChangeLog." to skip the proper ChangeLog-less removals.
next prev parent reply other threads:[~2011-04-30 9:01 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-30 8:46 [gentoo-dev] Devmanual text on ChangeLogs Petteri Räty
2011-04-30 9:02 ` Samuli Suominen [this message]
2011-04-30 12:12 ` Peter Volkov
2011-05-02 2:23 ` Jeroen Roovers
2011-04-30 13:42 ` Markos Chandras
2011-04-30 14:24 ` Brian Harring
2011-04-30 18:16 ` Alex Alexander
2011-04-30 20:39 ` Panagiotis Christopoulos
2011-05-01 9:06 ` Samuli Suominen
2011-05-01 10:09 ` [gentoo-dev] git? [was: Re: Devmanual text on ChangeLogs] Eray Aslan
2011-05-01 10:54 ` [gentoo-dev] git? Panagiotis Christopoulos
2011-05-01 11:25 ` Andreas K. Huettel
2011-05-01 18:05 ` [gentoo-dev] git? [was: Re: Devmanual text on ChangeLogs] Maciej Mrozowski
2011-05-01 10:34 ` [gentoo-dev] Devmanual text on ChangeLogs Fabian Groffen
2011-05-01 10:44 ` Panagiotis Christopoulos
2011-05-01 11:26 ` Peter Volkov
2011-05-01 11:26 ` Andreas K. Huettel
2011-05-01 20:43 ` Brian Harring
2011-05-02 2:43 ` Jeroen Roovers
2011-04-30 9:07 ` Ulrich Mueller
2011-04-30 11:21 ` Panagiotis Christopoulos
2011-05-02 2:52 ` Jeroen Roovers
2011-04-30 12:28 ` [gentoo-dev] " Diego Elio Pettenò
2011-04-30 13:05 ` Panagiotis Christopoulos
2011-04-30 13:44 ` "Paweł Hajdan, Jr."
2011-04-30 14:00 ` Rich Freeman
2011-04-30 9:57 ` [gentoo-dev] " Pacho Ramos
2011-05-01 10:00 ` Fabian Groffen
2011-05-01 14:55 ` [gentoo-dev] " Duncan
2011-05-01 15:08 ` Fabian Groffen
2011-05-01 21:08 ` [gentoo-dev] " Markos Chandras
2011-05-01 22:33 ` Brian Harring
2011-05-01 22:49 ` Markos Chandras
2011-05-01 23:23 ` [gentoo-dev] " Duncan
2011-05-01 23:31 ` Brian Harring
2011-05-01 23:43 ` Rich Freeman
2011-05-02 0:13 ` Markos Chandras
2011-05-02 1:15 ` Duncan
2011-05-02 6:48 ` Fabian Groffen
2011-05-02 0:16 ` Markos Chandras
2011-05-02 21:10 ` Arfrever Frehtes Taifersar Arahesis
2011-05-01 23:11 ` Duncan
2011-05-02 0:04 ` [gentoo-dev] " Ulrich Mueller
2011-05-02 0:21 ` Markos Chandras
2011-05-02 1:20 ` Nirbheek Chauhan
2011-05-02 1:24 ` Robin H. Johnson
2011-05-02 1:37 ` Nirbheek Chauhan
2011-05-02 5:17 ` Ulrich Mueller
2011-05-02 6:51 ` Fabian Groffen
2011-05-02 21:24 ` Gilles Dartiguelongue
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=4DBBD02B.3060909@gentoo.org \
--to=ssuominen@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