*.svg = svn:eol-style=native;svn:mime-type=text/plain
=== The svnci script svn2cl ===The Gramps project does not keep a ChangeLog file under source control. All change history is captured by Subversion automatically when it is committed. A ChangeLog file is generated from the SVN commit logs before each release using svn2cl. Developers should take care to make useful script for helping you commit log messages when committing changes is <code>svnci</code>to Subversion. Here are some guidelines: [[Media:Svnci.tar.gz|Download svnci]]
Usage:*Try to make a descriptive message about the change.*place svnci in your root svn directory, eg <code>gramps22</code> or <code>gramps30</code> (chmod +x)Use complete sentences when possible.*you '''need''' to have When committing a change that fixes a bug on the ''patchutils'' package installedtracker, or svnci will throw an error (use the bug''filterdiff'' is needed)s number and summary as the message.*do edits When committing a patch from a contributer, put the contributor's name and e-mail address in the commit new filesmessage.*edit the Changelog file with your edits*to commit changes It is not necessary to put the svn repository, go to names of the root directory, and do <code>./svnci</code>. This will collect all changes, and upload files you have modified in the change. The log commit message will be taken from the Changelogbecause Subversion stores that automatically.
=== Other usage tips ===
* Additional tips and recommndations recommendations related to committing changes: [[SVN Commit Tips]]
=== Browse svn ===
