Difference between revisions of "Svn practices"
Line 4: | Line 4: | ||
− | == Read-only access == | + | ==Read-only access== |
Grab the whole source code | Grab the whole source code | ||
Line 17: | Line 17: | ||
− | == Write access == | + | ==Write access== |
There is a guide for new committers: | There is a guide for new committers: | ||
http://www.apache.org/dev/new-committers-guide.html | http://www.apache.org/dev/new-committers-guide.html | ||
Line 42: | Line 42: | ||
and the Merging section has some complete | and the Merging section has some complete | ||
− | == Reference == | + | ==Reference== |
Merge Instruction from FreeBSD: | Merge Instruction from FreeBSD: | ||
http://wiki.freebsd.org/SubversionPrimer/Merging | http://wiki.freebsd.org/SubversionPrimer/Merging |
Revision as of 06:28, 5 June 2012
This page is still under review.
This page gathered svn practices frequently used by contributors and committers. If you have any advice to this page, please feel free to update it or post your idea in ooo-dev mail list.
Read-only access
Grab the whole source code
Grab a branche
Update your tree
Update to a specific revision
Check changes in specific revision
Write access
There is a guide for new committers: http://www.apache.org/dev/new-committers-guide.html
Commit your changes
Check changes before commit
Specify in the command line a list of the files/dirs that are changed to avoid accidentally committing unwanted changes.
Template for the log files should be used
svn commit ci -F ../mychangelog.txt change1 change2
Do not use 'svn commit -m "Your comment".
Update bugzilla with revision information for crossreference when you are done with the commit
How to create a branche of your own. When it comes to big or complicated changes, you may don't want to commit in stable branch directly.
How to merge your changes
For reference, FreeBSD has a SVN Primer, and the Merging section has some complete
Reference
Merge Instruction from FreeBSD: http://wiki.freebsd.org/SubversionPrimer/Merging