[27876] trunk/base/portmgr/ReleaseProcess

source_changes at macosforge.org source_changes at macosforge.org
Wed Aug 15 10:17:22 PDT 2007


Revision: 27876
          http://trac.macosforge.org/projects/macports/changeset/27876
Author:   jmpp at macports.org
Date:     2007-08-15 10:17:22 -0700 (Wed, 15 Aug 2007)

Log Message:
-----------
Rephrase a bit the comment on svnmerge.py

Modified Paths:
--------------
    trunk/base/portmgr/ReleaseProcess

Modified: trunk/base/portmgr/ReleaseProcess
===================================================================
--- trunk/base/portmgr/ReleaseProcess	2007-08-15 17:12:54 UTC (rev 27875)
+++ trunk/base/portmgr/ReleaseProcess	2007-08-15 17:17:22 UTC (rev 27876)
@@ -49,9 +49,9 @@
 
 Only the base subdirectory, not the ports subdirectory, is branched for a given release.
 
-It is strongly recommended to use the svnmerge.py tool provided by the subversion project to
-maintain release branches if you pretend to merge revisions back and forth between them and
-trunk/base, which is a very likely scenario.
+It is strongly recommended to use the svnmerge.py tool (provided by the subversion port) to
+maintain merge tracking information between release branches and trunk/base if you pretend to
+merge revisions back and forth between them, which is a very likely scenario.
 
 
 === Prepare the code for Release ===

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


More information about the macports-changes mailing list