{ "content": [ { "type": "text", "text": "# SVN_LOAD_DIRS (man)\n\n**Summary:** svnloaddirs - Load directories into a Subversion repository\n\n**Synopsis:** svnloaddirs [options] svnurl svnimportdir [directory ...]\n\n## Flags\n\n| Flag | Long | Arg | Description |\n|------|------|-----|-------------|\n| — | — | — | Don't ask any questions. Assume that the answer is yes. |\n| -p | — | — | Apply the properties specified in the configuration file filename to matching files. See below for a description of the |\n| — | — | — | Username to use when committing to the repository. |\n| — | — | — | Password to use when committing to the repository. |\n| -t | — | — | Create a tag copy in tagdir, relative to svnurl. tagdir may contain a regular ex‐ pression enclosed within '@' character |\n| -v | — | — | |\n| — | — | — | Use the already checked out working copy at path instead of checking out a new working copy. |\n\n## Examples\n\n- `For example, to import the contents of the foo-1.3 directory into the upstream/current direc‐`\n- `tory of the foo repository:`\n- `svnloaddirs svn+ssh://svn.example.org/svn/foo upstream/current foo-1.3`\n- `A tag can also be added automatically using the -t option:`\n- `svnloaddirs svn+ssh://svn.example.org/svn/foo -t 'upstream/@\\d+\\.\\w+@' upstream/current`\n- `foo-1.3`\n- `Here's an example of a property configuration file:`\n- `\\.doc$ break svn:mime-type application/msword`\n- `\\.ds(p|w)$ break svn:eol-style CRLF`\n- `\\.dos2unix-eol\\.sh$ break`\n- `.* break svn:eol-style native`\n- `This example specifies that .doc files are to be treated as binary files, that .dsp and .dsw`\n- `files have their line ending characters kept, and that all other files except dos2unix-eol.sh`\n- `have their line endings converted to the native style.`\n\n## See Also\n\n- svn(1)\n\n## Section Outline\n\n- **NAME** (3 lines)\n- **SYNOPSIS** (3 lines)\n- **DESCRIPTION** (7 lines)\n- **OPTIONS** (10 lines) — 7 subsections\n - -no (2 lines)\n - -p (3 lines)\n - -svn (2 lines)\n - -svn (2 lines)\n - -t (4 lines)\n - -v (1 lines)\n - -wc (4 lines)\n- **PROPERTY CONFIGURATION FILE FORMAT** (29 lines)\n- **EXAMPLES** (22 lines)\n- **SEE ALSO** (5 lines)\n- **AUTHOR** (6 lines)\n\n## Full Content\n\n### NAME\n\nsvnloaddirs - Load directories into a Subversion repository\n\n### SYNOPSIS\n\nsvnloaddirs [options] svnurl svnimportdir [directory ...]\n\n### DESCRIPTION\n\nThis tool can be used for importing one or more directories into a Subversion repository. The\ndifference from \"svn import\" is that svnloaddirs can update an existing directory tree, and\ntag it properly. Only changes from the previous version will be recorded in the revision, so\nthat you can easily apply them on another branch. For example, this is very useful for man‐\naging the upstream source when maintaining Debian packages in Subversion.\n\n### OPTIONS\n\nsvnurl\nThe base Subversion URL.\n\nsvnimportdir\nThe path relative to svnurl where the directories are to be imported.\n\ndirectory ...\nThe directories to import. If they are not specified on the command line, they are\nread from standard input.\n\n#### -no\n\nDon't ask any questions. Assume that the answer is yes.\n\n#### -p\n\nApply the properties specified in the configuration file filename to matching files.\nSee below for a description of the configuration file format.\n\n#### -svn\n\nUsername to use when committing to the repository.\n\n#### -svn\n\nPassword to use when committing to the repository.\n\n#### -t\n\nCreate a tag copy in tagdir, relative to svnurl. tagdir may contain a regular ex‐\npression enclosed within '@' characters. It will be replaced by the matching part from\nthe imported directory names.\n\n#### -v\n\n#### -wc\n\nUse the already checked out working copy at path instead of checking out a new working\ncopy.\n\n### PROPERTY CONFIGURATION FILE FORMAT\n\nThe property configuration file, which is specified by the -p option, contains rules for ap‐\nplying properties to the imported files. It consists of lines of the following format:\n\nregularexpression control propertyname propertyvalue\n\nThe meaning of the fields are:\n\nregularexpression\nA Perl-style regular expression matching the files to apply this rule to.\n\ncontrol\nEither \"break\" or \"cont\". If set to \"break\", processing of the current file will stop\nif this rule matches. If set to \"cont\", processing will continue. The latter can be\nused to set multiple properties for one file.\n\npropertyname\n(Optional) The name of the property to set.\n\npropertyvalue\n(Optional) Set the property to this value.\n\nThe last two fields may be omitted, in which case the rule will not set any properties. This\nis useful for excluding certain files from subsequent rules.\n\nYou need to quote the regularexpression, propertyname and propertyvalue fields with double\nquotes ('\"') if you have whitespace in them. Single and double quotes can be escaped with\nbackslash ('\\').\n\n### EXAMPLES\n\nFor example, to import the contents of the foo-1.3 directory into the upstream/current direc‐\ntory of the foo repository:\n\nsvnloaddirs svn+ssh://svn.example.org/svn/foo upstream/current foo-1.3\n\nA tag can also be added automatically using the -t option:\n\nsvnloaddirs svn+ssh://svn.example.org/svn/foo -t 'upstream/@\\d+\\.\\w+@' upstream/current\nfoo-1.3\n\nHere's an example of a property configuration file:\n\n\\.doc$ break svn:mime-type application/msword\n\\.ds(p|w)$ break svn:eol-style CRLF\n\\.dos2unix-eol\\.sh$ break\n.* break svn:eol-style native\n\nThis example specifies that .doc files are to be treated as binary files, that .dsp and .dsw\nfiles have their line ending characters kept, and that all other files except dos2unix-eol.sh\nhave their line endings converted to the native style.\n\n### SEE ALSO\n\n/usr/share/doc/subversion-tools/svnloaddirs.README.gz\n\nsvn(1)\n\n### AUTHOR\n\nThis manual page was written by Per Olofsson for the Debian distribution\n(but may be used by others). Some parts were taken from the README.\n\n\n\nSVNLOADDIRS(1)\n\n" } ], "structuredContent": { "command": "SVN_LOAD_DIRS", "section": "", "mode": "man", "summary": "svnloaddirs - Load directories into a Subversion repository", "synopsis": "svnloaddirs [options] svnurl svnimportdir [directory ...]", "tldr_summary": null, "tldr_examples": [], "tldr_source": null, "flags": [ { "flag": "", "long": null, "arg": null, "description": "Don't ask any questions. Assume that the answer is yes." }, { "flag": "-p", "long": null, "arg": null, "description": "Apply the properties specified in the configuration file filename to matching files. See below for a description of the configuration file format." }, { "flag": "", "long": null, "arg": null, "description": "Username to use when committing to the repository." }, { "flag": "", "long": null, "arg": null, "description": "Password to use when committing to the repository." }, { "flag": "-t", "long": null, "arg": null, "description": "Create a tag copy in tagdir, relative to svnurl. tagdir may contain a regular ex‐ pression enclosed within '@' characters. It will be replaced by the matching part from the imported directory names." }, { "flag": "-v", "long": null, "arg": null, "description": "" }, { "flag": "", "long": null, "arg": null, "description": "Use the already checked out working copy at path instead of checking out a new working copy." } ], "examples": [ "For example, to import the contents of the foo-1.3 directory into the upstream/current direc‐", "tory of the foo repository:", "svnloaddirs svn+ssh://svn.example.org/svn/foo upstream/current foo-1.3", "A tag can also be added automatically using the -t option:", "svnloaddirs svn+ssh://svn.example.org/svn/foo -t 'upstream/@\\d+\\.\\w+@' upstream/current", "foo-1.3", "Here's an example of a property configuration file:", "\\.doc$ break svn:mime-type application/msword", "\\.ds(p|w)$ break svn:eol-style CRLF", "\\.dos2unix-eol\\.sh$ break", ".* break svn:eol-style native", "This example specifies that .doc files are to be treated as binary files, that .dsp and .dsw", "files have their line ending characters kept, and that all other files except dos2unix-eol.sh", "have their line endings converted to the native style." ], "see_also": [ { "name": "svn", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/svn/1/json" } ], "section_outline": [ { "name": "NAME", "lines": 3, "subsections": [] }, { "name": "SYNOPSIS", "lines": 3, "subsections": [] }, { "name": "DESCRIPTION", "lines": 7, "subsections": [] }, { "name": "OPTIONS", "lines": 10, "subsections": [ { "name": "-no", "lines": 2 }, { "name": "-p", "lines": 3, "flag": "-p" }, { "name": "-svn", "lines": 2 }, { "name": "-svn", "lines": 2 }, { "name": "-t", "lines": 4, "flag": "-t" }, { "name": "-v", "lines": 1, "flag": "-v" }, { "name": "-wc", "lines": 4 } ] }, { "name": "PROPERTY CONFIGURATION FILE FORMAT", "lines": 29, "subsections": [] }, { "name": "EXAMPLES", "lines": 22, "subsections": [] }, { "name": "SEE ALSO", "lines": 5, "subsections": [] }, { "name": "AUTHOR", "lines": 6, "subsections": [] } ], "sections": { "NAME": { "content": "svnloaddirs - Load directories into a Subversion repository\n\n", "subsections": [] }, "SYNOPSIS": { "content": "svnloaddirs [options] svnurl svnimportdir [directory ...]\n\n", "subsections": [] }, "DESCRIPTION": { "content": "This tool can be used for importing one or more directories into a Subversion repository. The\ndifference from \"svn import\" is that svnloaddirs can update an existing directory tree, and\ntag it properly. Only changes from the previous version will be recorded in the revision, so\nthat you can easily apply them on another branch. For example, this is very useful for man‐\naging the upstream source when maintaining Debian packages in Subversion.\n\n", "subsections": [] }, "OPTIONS": { "content": "svnurl\nThe base Subversion URL.\n\nsvnimportdir\nThe path relative to svnurl where the directories are to be imported.\n\ndirectory ...\nThe directories to import. If they are not specified on the command line, they are\nread from standard input.\n", "subsections": [ { "name": "-no", "content": "Don't ask any questions. Assume that the answer is yes.\n" }, { "name": "-p", "content": "Apply the properties specified in the configuration file filename to matching files.\nSee below for a description of the configuration file format.\n", "flag": "-p" }, { "name": "-svn", "content": "Username to use when committing to the repository.\n" }, { "name": "-svn", "content": "Password to use when committing to the repository.\n" }, { "name": "-t", "content": "Create a tag copy in tagdir, relative to svnurl. tagdir may contain a regular ex‐\npression enclosed within '@' characters. It will be replaced by the matching part from\nthe imported directory names.\n", "flag": "-t" }, { "name": "-v", "content": "", "flag": "-v" }, { "name": "-wc", "content": "Use the already checked out working copy at path instead of checking out a new working\ncopy.\n\n" } ] }, "PROPERTY CONFIGURATION FILE FORMAT": { "content": "The property configuration file, which is specified by the -p option, contains rules for ap‐\nplying properties to the imported files. It consists of lines of the following format:\n\nregularexpression control propertyname propertyvalue\n\nThe meaning of the fields are:\n\nregularexpression\nA Perl-style regular expression matching the files to apply this rule to.\n\ncontrol\nEither \"break\" or \"cont\". If set to \"break\", processing of the current file will stop\nif this rule matches. If set to \"cont\", processing will continue. The latter can be\nused to set multiple properties for one file.\n\npropertyname\n(Optional) The name of the property to set.\n\npropertyvalue\n(Optional) Set the property to this value.\n\nThe last two fields may be omitted, in which case the rule will not set any properties. This\nis useful for excluding certain files from subsequent rules.\n\nYou need to quote the regularexpression, propertyname and propertyvalue fields with double\nquotes ('\"') if you have whitespace in them. Single and double quotes can be escaped with\nbackslash ('\\').\n\n", "subsections": [] }, "EXAMPLES": { "content": "For example, to import the contents of the foo-1.3 directory into the upstream/current direc‐\ntory of the foo repository:\n\nsvnloaddirs svn+ssh://svn.example.org/svn/foo upstream/current foo-1.3\n\nA tag can also be added automatically using the -t option:\n\nsvnloaddirs svn+ssh://svn.example.org/svn/foo -t 'upstream/@\\d+\\.\\w+@' upstream/current\nfoo-1.3\n\nHere's an example of a property configuration file:\n\n\\.doc$ break svn:mime-type application/msword\n\\.ds(p|w)$ break svn:eol-style CRLF\n\\.dos2unix-eol\\.sh$ break\n.* break svn:eol-style native\n\nThis example specifies that .doc files are to be treated as binary files, that .dsp and .dsw\nfiles have their line ending characters kept, and that all other files except dos2unix-eol.sh\nhave their line endings converted to the native style.\n\n", "subsections": [] }, "SEE ALSO": { "content": "/usr/share/doc/subversion-tools/svnloaddirs.README.gz\n\nsvn(1)\n\n", "subsections": [] }, "AUTHOR": { "content": "This manual page was written by Per Olofsson for the Debian distribution\n(but may be used by others). Some parts were taken from the README.\n\n\n\nSVNLOADDIRS(1)", "subsections": [] } } } }