В Пнд, 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.
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>
