From: Peter Volkov <pva@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: RFC: better policy for ChageLogs (was: Re: [gentoo-dev] Council May Summary: Changes to ChangeLog handling)
Date: Wed, 01 Jun 2011 19:08:23 +0400 [thread overview]
Message-ID: <1306940903.4416.20.camel@tablet> (raw)
In-Reply-To: <20110530215552.GA3908@hrair>
[-- Attachment #1: Type: text/plain, Size: 571 bytes --]
В Пнд, 30/05/2011 в 14:55 -0700, Brian Harring пишет:
> The problem is, that's a *fuzzy* definition.
Ok, let's start with something and then we'll add more items if
required. Currently I'd like to propose following text:
The ChangeLog must be updated with each commit. The only possible
relaxations for this rule are:
1. Nonfunctional whitespace changes
2. Changes in comments (lines starting with # in ebuild, or leading text
in patches)
3. Manifest updates
4. Changes in ChageLog itself ;)
Something unclear? Anything else?
--
Peter.
[-- Attachment #2: text.xml.patch --]
[-- Type: text/x-patch, Size: 1056 bytes --]
diff --git a/ebuild-writing/misc-files/changelog/text.xml b/ebuild-writing/misc-files/changelog/text.xml
index d92bbf4..eea927e 100644
--- a/ebuild-writing/misc-files/changelog/text.xml
+++ b/ebuild-writing/misc-files/changelog/text.xml
@@ -5,10 +5,21 @@
<body>
<p>
-The <c>ChangeLog</c> must be updated with each commit. The
-echangelog tool should be used to create <c>ChangeLog</c> entries;
-the format of a <c>ChangeLog</c> is now defined as "whatever
-<c>echangelog</c> creates".
+The <c>ChangeLog</c> must be updated with each commit. The only possible
+relaxations for this rule are:
+</p>
+
+<ul>
+ <li><b>1.</b> Nonfunctional whitespace changes</li>
+ <li><b>2.</b> Changes in comments (lines starting with # in ebuild, or leading text in patches)</li>
+ <li><b>3.</b> Manifest updates</li>
+ <li><b>4.</b> Changes in <c>ChageLog</c> itself ;)</li>
+</ul>
+
+<p>
+The echangelog tool should be used to create <c>ChangeLog</c> entries; the
+format of a <c>ChangeLog</c> is now defined as "whatever <c>echangelog</c>
+creates".
</p>
<p>
next prev parent reply other threads:[~2011-06-01 16:04 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
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 ` Peter Volkov [this message]
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=1306940903.4416.20.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