This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
* subversion/bindings/swig/python/tests/repository.py (DumpStreamParser.__init__): Hold pool object if it is passed. (DumpStreamParser._close_dumpstream): Release the pool. (SubversionRepositoryTestCase.test_parse_fns3): Add test for parse_fns3 baton reference leak (SVN-4918) git-svn-id: https://svn.apache.org/repos/asf/subversion/trunk@1912517 13f79535-47bb-0310-9956-ffa450edef68
Failed to load latest commit information.
Subversion, a version control system. ===================================== $LastChangedDate$ Contents: I. A FEW POINTERS II. DOCUMENTATION III. PARTICIPATING IN THE SUBVERSION COMMUNITY IV. QUICKSTART GUIDE V. CONVERTING FROM CVS I. A FEW POINTERS For an overview of the Subversion project, visit https://subversion.apache.org/ Once you have a Subversion client you can get the latest version of the code with the command: $ svn co https://svn.apache.org/repos/asf/subversion/trunk subversion II. DOCUMENTATION The main documentation is the Subversion Book - an on-line version can be found at: https://svnbook.red-bean.com/ It is written in DocBook XML, and the sources can be found at: https://svn.code.sf.net/p/svnbook/source/trunk/ If you wish to build the documentation from source, read the en/README file within the book source. III. PARTICIPATING IN THE SUBVERSION COMMUNITY First, read https://subversion.apache.org/docs/community-guide/ It describes Subversion coding and log message standards, as well as how to join discussion lists. Talk on IRC with developers: irc.libera.chat, channel #svn-dev. Read the FAQ: https://subversion.apache.org/faq.html IV. QUICKSTART GUIDE See the final section of the first chapter of the Subversion Book. V. CONVERTING FROM CVS If you're a CVS user trying to move your CVS history over to Subversion, then be sure to visit the 'cvs2svn' project: https://github.com/mhagger/cvs2svn If you are running a Linux or BSD-based system, your distribution might have a cvs2svn package. If cvs2svn doesn't meet your needs, you might try refinecvs written by Lev Serebryakov: http://lev.serebryakov.spb.ru/refinecvs/ Please note that cvs2svn and refinecvs are *separate* projects from Subversion. If you have problems or are confused, contact the authors, not the Subversion lists. Finally, be sure to see Appendix B in the Subversion Book. It contains a very quick overview of the major differences between CVS and Subversion.
No packages published