ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #subversion
Decide whether to use the lightweight svnserve daemon or Apache HTTPD with mod_dav_svn for your Subversion server, based on network, auth, and feature needs.
Learn how to eliminate duplicated code by declaring shared directories with Subversion's svn:externals property, see a concrete setup example, and understand the trade‑offs of floating vs. pinned externals.
A concise decision guide for choosing between Subversion's per‑directory svn:ignore property and the global‑ignores runtime setting, with a table of trade‑offs, an implementation example, and verification steps.
Learn how to use Subversion’s sparse checkout to check out only the directories you need, reducing disk usage and update time while keeping the ability to expand or shrink the view later.
Subversion tracks branch integration with svn:mergeinfo. Learn how merge tracking avoids double-merges, when cherry-picking creates property bloat, and how to safely inspect and dry-run a merge before committing.
Learn how to use Subversion's svn:externals property to link external repositories into your working copy, pin revisions, and avoid common pitfalls.
Stop downloading gigabytes of unnecessary data. Learn how to use SVN sparse checkouts and --set-depth to optimize your local workspace in monolithic repositories.
Decide whether to pin Subversion externals to a specific revision or let them track the latest changes. A concise decision guide, trade‑off table, and hands‑on example help you pick the right strategy for reproducible builds and maintenance.
Learn how Subversion’s svn:externals lets you reference external paths, avoid duplication, and keep dependencies in sync. Follow step‑by‑step setup, pitfalls, and best‑practice tips.
apache