Subversion Dev
- 1.10 task: error leaks
- 1.10 task: update 'Roadmap' page
- 1.10 tasks: update CHANGES and roll RC1 or beta1
- 1.10-dev doxygen not rebuilt recently
- [PATCH] issue #4375: provide --password-fd option
- [PATCH] release.py: write-changelog function (POC)
- [PATCH] Use the `WITHOUT ROWID` SQLite optimization for rep-cache.db
- A server-side merkle-tree capability for ordinary Subversion* installs.
- Authz - paths with trailing slash isn't supported - right?
- Authz suggestion
- Automating create-a-release-branch
- Bash completion updates
- Bash completion updates)
- Checkpointing v1 in diagrams
- Feature suggestion: determination of the subversion commit number for a directory (over DAV without svn clients involved)
- Ideas for tracking Authz changes in a repo
- JDK 10 removal of javah
- Let's switch to time-based releases
- list --search matching and Windows *-expansion
- lz4)
- Migrating our wiki to Confluence
- Potential regression: high server-side memory consumption during import (was: Subversion 1.10 RC1?)
- Refreshing / redesigning our website
- Reviewing 1.10 APIs & compatibility
- shelve is (surprisingly) sensitive to working directory
- Subversion 1.10 RC1?
- subversion support for APR 1.6 missing for windows?
- svn commit: r1807836 - in /subversion/trunk: subversion/include/ subversion/include/private/ subversion/libsvn_repos/ subversion/svnadmin/ subversion/svnrdump/ subversion/tests/cmdline/ subversion/tests/cmdline/svntest/ subversion/tests/libsvn_repos/ t...
- svn commit: r1813665 - in /subversion/branches/swig-py3: ./ build/ac-macros/ subversion/bindings/swig/ subversion/bindings/swig/include/ subversion/bindings/swig/python/libsvn_swig_py/
- svn commit: r1813898 [...])
- svn commit: r1816596 - /subversion/branches/swig-py3/Makefile.in
- svn commit: r1816774 - /subversion/site/staging/mailing-lists.html
- svn commit: r1816926 - /subversion/site/staging/docs/community-guide/mailing-lists.part.html
- svn commit: r1817032 - in /subversion/site/staging/docs: index.html release-notes/1.8.html
- svn commit: r1817146 - /subversion/site/staging/docs/release-notes/1.6.zh.html
- svn commit: r1817713 - in /subversion/site/staging/docs/release-notes: 1.6.html 1.6.zh.html
- svn commit: r1817718 - /subversion/site/staging/docs/index.html / Reinstate 1.6 API docu
- svn commit: r1817775 - /subversion/site/publish/docs/community-guide/releasing.part.html
- svn commit: r1817837 - in /subversion/trunk: CHANGES subversion/bindings/javahl/src/org/apache/subversion/javahl/NativeResources.java subversion/include/svn_version.h subversion/tests/cmdline/svntest/main.py
- svn commit: r1817862 - /subversion/site/staging/docs/release-notes/1.4.html
- svn commit: r1817969 - /subversion/site/staging/docs/release-notes/1.3.html
- svn commit: r1818340 - in /subversion/site/staging: faq.html faq.ja.html faq.zh.html
- svn commit: r1818343 - in /subversion/site/staging: faq.html faq.ja.html faq.zh.html
- svn commit: r1818496 - /subversion/site/staging/docs/release-notes/1.10.html
- svn commit: r1818578 - /subversion/trunk/subversion/libsvn_repos/list.c
- svn commit: r1818724 - /subversion/site/staging/faq.html
- svn commit: r1818995 - in /subversion/branches/swig-py3: build/ac-macros/swig.m4 subversion/bindings/swig/include/proxy.py subversion/bindings/swig/include/proxy.swg
- svn commit: r1819110 - /subversion/branches/swig-py3/subversion/bindings/swig/include/proxy.swg
- svn commit: r1819207 - /subversion/trunk/tools/dist/edit-N-log-messages
- svn commit: r1819391 - /subversion/site/staging/docs/release-notes/1.10.html
- svn propchange: r1818584 - svn:log
- svn_client_status6() and svn_client_patch_func_t doc strings
- svn_dirent_t.size API inconsistency
- svnignore?
- Swig py3 branch
- swig-py3 branch review for trunk merge
- Tree conflict 'svn merge' message
- Website 'staging' branch catch-up merges [was: svn commit: r1817775]
- »Ø¸´£º »Ø¸´£º why my process open .svn/tmp/svn-XXXXXX file? and why aretmpfiles deleted? and why my process can't open the right file after tmpfiles deleted?
[Subversion] ·
[svn.haxx.se]
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.