[31679] trunk/base/HACKING

jberry at macports.org jberry at macports.org
Sun Dec 2 16:17:21 PST 2007


Revision: 31679
          http://trac.macosforge.org/projects/macports/changeset/31679
Author:   jberry at macports.org
Date:     2007-12-02 16:17:18 -0800 (Sun, 02 Dec 2007)

Log Message:
-----------
Revisions to language in HACKING file

Modified Paths:
--------------
    trunk/base/HACKING

Modified: trunk/base/HACKING
===================================================================
--- trunk/base/HACKING	2007-12-02 23:22:49 UTC (rev 31678)
+++ trunk/base/HACKING	2007-12-03 00:17:18 UTC (rev 31679)
@@ -11,13 +11,12 @@
 
 # Commits to the "base" component of the repository:
 
-* Any commit made to the "base" component of the repository should be accompanied by a corresponding entry in the base/ChanegeLog file, full with information
-    of the svn revision information of the commit and Trac ticket number the commit references and/or fixes, if any.
+* Commits with user-visible affect made to the "base" component of the repository should be accompanied by a corresponding entry in the base/ChanegeLog file,
+  with references to pertitent Trac ticket numbers and svn commit revisions where appropriate.
 * Such entries to the ChangeLog need not be full duplications of their related commit logs if the latter are thorough explanations of what's involved in the commit.
-    In such cases it's perfectly acceptable to enter just a summary of the commit and point the reader to further information through the related svn revision
-    and Trac ticket number (if applicable).
-* Related commits to "base" may be grouped in a single ChangeLog entry, provided the full list of svn revisions and Trac ticket numbers referenced (if applicable)
-    is included.
+  In such cases it's perfectly acceptable to enter just a summary of the commit and point the reader to further information through the related svn revision
+  and Trac ticket number (if applicable).
+* Related commits to "base" should be grouped in a single ChangeLog entry.
 * Commits to "base" need not update the base/NEWS file, as such will be constructed with the relevant information at MacPorts release time by the release engineers.
 
 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.macosforge.org/pipermail/macports-changes/attachments/20071202/a3edc129/attachment.html


More information about the macports-changes mailing list