pim schravendijk a écrit : > Now if I would like to put this back to the SVN system, can I use the > info written in > http://wiki.jmol.org/index.php/Release_Procedures#Release_build? Some > of the text there seems not to fit, e.g.: > > What is the preferred text to use as the commit message? > the page says: svn commit -m "prerelease 10.3.1", but I wouldn't know > on what prerelease I would be working. > Also the svn copy commands don't seem to apply to my case. > The page you are refering to is mostly a reminder for admins on what to do exactly when we needed to do a new release of Jmol (available on sourceforge in the download section). That's why some of the text doesn't fit with committing a bug fix or a new feature ;)
For the text, try to use a (short but) descriptive text of the modification, so that when when browsing through the history of modification we know what to expect in the modification. There's no description on how to check out / update / commit on the Wiki (nobody thought of adding it before apparently), except on the Eclipse page. If you have troubles, tell me. Nico ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Jmol-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jmol-developers
