diff options
| author | Eric Wong <normalperson@yhbt.net> | 2007-02-18 02:34:09 -0800 |
|---|---|---|
| committer | Eric Wong <normalperson@yhbt.net> | 2007-02-23 00:57:13 -0800 |
| commit | 0dfaf0a4e1905a9137d3f2f691620529aeb3b4fa (patch) | |
| tree | 014cc67e9070476560f97c983a850267156295de /Documentation | |
| parent | a81ed0b63edb0d473e17e078de2269b735156a79 (diff) | |
| download | git-0dfaf0a4e1905a9137d3f2f691620529aeb3b4fa.tar.gz git-0dfaf0a4e1905a9137d3f2f691620529aeb3b4fa.tar.xz | |
git-svn: allow metadata options to be specified with 'init' and 'clone'
Since the options that affect the way metadata is handled in
git-svn, should be consistently set/unset throughout history
imported by git-svn; it makes sense to allow the user to set
certain options from the command-line that will write to the
config file when initially creating the repository.
Also, fix some formatting issues while we're updating
documentation.
Signed-off-by: Eric Wong <normalperson@yhbt.net>
Diffstat (limited to 'Documentation')
| -rw-r--r-- | Documentation/git-svn.txt | 24 |
1 files changed, 16 insertions, 8 deletions
diff --git a/Documentation/git-svn.txt b/Documentation/git-svn.txt index bd163cfad..da68f6d73 100644 --- a/Documentation/git-svn.txt +++ b/Documentation/git-svn.txt @@ -49,6 +49,15 @@ COMMANDS (--tags=project/tags') or a full url (--tags=https://foo.org/project/tags) +--no-metadata:: + Set the 'noMetadata' option in the [svn-remote] config. +--use-svm-props:: + Set the 'useSvmProps' option in the [svn-remote] config. +--use-svnsync-props:: + Set the 'useSvnsyncProps' option in the [svn-remote] config. +--rewrite-root=<URL>:: + Set the 'rewriteRoot' option in the [svn-remote] config. + --prefix=<prefix> This allows one to specify a prefix which is prepended to the names of remotes if trunk/branches/tags are @@ -307,8 +316,8 @@ CONFIG FILE-ONLY OPTIONS ------------------------ -- -svn.noMetadata: -svn-remote.<name>.noMetadata: +svn.noMetadata:: +svn-remote.<name>.noMetadata:: This gets rid of the git-svn-id: lines at the end of every commit. If you lose your .git/svn/git-svn/.rev_db file, git-svn will not @@ -319,8 +328,8 @@ svn-remote.<name>.noMetadata: this, either. Using this conflicts with the 'useSvmProps' option for (hopefully) obvious reasons. -svn.useSvmProps: -svn-remote.<name>.useSvmProps: +svn.useSvmProps:: +svn-remote.<name>.useSvmProps:: This allows git-svn to re-map repository URLs and UUIDs from mirrors created using SVN::Mirror (or svk) for metadata. @@ -332,20 +341,19 @@ svn-remote.<name>.useSvmProps: URL and UUID, and use it when generating metadata in commit messages. -svn.useSvnsyncProps: -svn-remote.<name>.useSvnsyncprops: +svn.useSvnsyncProps:: +svn-remote.<name>.useSvnsyncprops:: Similar to the useSvmProps option; this is for users of the svnsync(1) command distributed with SVN 1.4.x and later. -svn-remote.<name>.rewriteRoot +svn-remote.<name>.rewriteRoot:: This allows users to create repositories from alternate URLs. For example, an administrator could run git-svn on the server locally (accessing via file://) but wish to distribute the repository with a public http:// or svn:// URL in the metadata so users of it will see the public URL. - Since the noMetadata, rewriteRoot, useSvnsyncProps and useSvmProps options all affect the metadata generated and used by git-svn; they *must* be set in the configuration file before any history is imported |