forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: rev 9355 - xml/forrest/trunk/etc
Date Thu, 11 Mar 2004 08:23:12 GMT
Author: crossley
Date: Thu Mar 11 00:23:10 2004
New Revision: 9355

Modified:
   xml/forrest/trunk/etc/relicense.txt
Log:
Add some notes about how to do it.


Modified: xml/forrest/trunk/etc/relicense.txt
==============================================================================
--- xml/forrest/trunk/etc/relicense.txt	(original)
+++ xml/forrest/trunk/etc/relicense.txt	Thu Mar 11 00:23:10 2004
@@ -1,5 +1,25 @@
 The relicense task is described at
 http://issues.cocoondev.org/jira/secure/ViewIssue.jspa?key=FOR-123
+
+------------------------------------------------------------------------
+Here is one technique ...
+* Do the whole tree, a section at a time, using insert_license.pl script.
+* cd to a directory as high as you dare, e.g. src/documentation/
+* In another window, do a practice run:
+insert_license.pl -p /path/to/svn/forrest/src/documentation 2002-2004 > relicense.log
+* Review the summary output and grep the relicence.log file.
+* Investigate the files that are listed as having problems.
+* When happy do a production run:
+insert_license.pl /path/to/svn/forrest/src/documentation 2002-2004 > relicense.log
+* Again review the summary output and grep the relicence.log file.
+* Note any files that need fixing by hand (see etc/relicense.log).
+* Do a 'svn diff' and make sure it is what you expected, then 'svn commit'.
+
+* At some stage, use the Java or Python "relicense" script. This only deals
+with the *.java files.
+
+* Tweak the insert_license.pl script to address new issues.
+
 ------------------------------------------------------------------------
 This is a list of files that we need to ensure do *not* get a new license
 accidently inserted. If you notice any more in your travels then please

Mime
View raw message