{
    "mode": "man",
    "parameter": "SVNPATH",
    "section": "",
    "url": "https://www.chedong.com/phpMan.php/man/SVNPATH/json",
    "generated": "2026-06-16T10:47:31Z",
    "synopsis": "",
    "sections": {
        "NAME": {
            "content": "svnpath - output svn url with support for tags and branches\n",
            "subsections": []
        },
        "SYNOPSIS": {
            "content": "",
            "subsections": [
                {
                    "name": "svnpath",
                    "content": ""
                },
                {
                    "name": "svnpath tags",
                    "content": ""
                },
                {
                    "name": "svnpath branches",
                    "content": ""
                },
                {
                    "name": "svnpath trunk",
                    "content": ""
                }
            ]
        },
        "DESCRIPTION": {
            "content": "svnpath is intended to be run in a Subversion working copy.\n\nIn its simplest usage, svnpath with no parameters outputs the svn url for the repository\nassociated with the working copy.\n\nIf a parameter is given, svnpath attempts to instead output the url that would be used for\nthe tags, branches, or trunk. This will only work if it's run in the top-level directory that\nis subject to tagging or branching.\n\nFor example, if you want to tag what's checked into Subversion as version 1.0, you could use\na command like this:\n\nsvn cp $(svnpath) $(svnpath tags)/1.0\n\nThat's much easier than using svn info to look up the repository url and manually modifying\nit to derive the url to use for the tag, and typing in something like this:\n\nsvn cp svn+ssh://my.server.example/svn/project/trunk svn+ssh://my.server.example/svn/project/tags/1.0\n\nsvnpath uses a simple heuristic to convert between the trunk, tags, and branches paths. It\nreplaces the first occurrence of trunk, tags, or branches with the name of what you're\nlooking for. This will work ok for most typical Subversion repository layouts.\n\nIf you have an atypical layout and it does not work, you can add a ~/.svnpath file. This file\nis perl code, which can modify the path in $url.  For example, the author uses this file:\n\n#!/usr/bin/perl\n# svnpath personal override file\n\n# For d-i I sometimes work from a full d-i tree branch. Remove that from\n# the path to get regular tags or branches directories.\n$url=~s!d-i/(rc|beta)[0-9]+/!!;\n$url=~s!d-i/sarge/!!;\n1\n",
            "subsections": []
        },
        "LICENSE": {
            "content": "GPL version 2 or later\n",
            "subsections": []
        },
        "AUTHOR": {
            "content": "Joey Hess <joey@kitenet.net>\n\n\n\nDebian Utilities                             2026-03-04                                   SVNPATH(1)",
            "subsections": []
        }
    },
    "summary": "svnpath - output svn url with support for tags and branches",
    "flags": [],
    "examples": [],
    "see_also": []
}