path: root/Documentation/git-svn.txt
diff options
authorEric Wong <>2007-01-30 21:11:14 (GMT)
committerEric Wong <>2007-02-23 08:57:10 (GMT)
commitf0ecca1041aff2e1398edcdaf5f0ce08a96f5f0f (patch)
treee86c37d3ca3723b20fa97f813657fccc8d379d24 /Documentation/git-svn.txt
parent289370578ca5833641fbb59813173ac6db1986d1 (diff)
git-svn: remove the 'rebuild' command and make the functionality automatic
Since refs/remotes/* are not automatically cloned, we expect the user to be capable of copying those references themselves anyways. Also removed the documentation for --ignore-nodate while we're at it; it has also been made automatic. Signed-off-by: Eric Wong <>
Diffstat (limited to 'Documentation/git-svn.txt')
1 files changed, 3 insertions, 38 deletions
diff --git a/Documentation/git-svn.txt b/Documentation/git-svn.txt
index 6daba24..22dd7b2 100644
--- a/Documentation/git-svn.txt
+++ b/Documentation/git-svn.txt
@@ -93,16 +93,6 @@ remotes/git-svn.
commit. All merging is assumed to have taken place
independently of git-svn functions.
- Not a part of daily usage, but this is a useful command if
- you've just cloned a repository (using gitlink:git-clone[1]) that was
- tracked with git-svn. Unfortunately, git-clone does not clone
- git-svn metadata and the svn working tree that git-svn uses for
- its operations. This rebuilds the metadata so git-svn can
- resume fetch operations. A Subversion URL may be optionally
- specified at the command-line if the directory/repository you're
- tracking has moved or changed protocols.
Recursively finds and lists the svn:ignore property on
directories. The output is suitable for appending to
@@ -322,9 +312,9 @@ config key: svn.followparent
This gets rid of the git-svn-id: lines at the end of every commit.
- With this, you lose the ability to use the rebuild command. If
- you ever lose your .git/svn/git-svn/.rev_db file, you won't be
- able to fetch again, either. This is fine for one-shot imports.
+ If you lose your .git/svn/git-svn/.rev_db file, git-svn will not
+ be able to rebuild it and you won't be able to fetch again,
+ either. This is fine for one-shot imports.
The 'git-svn log' command will not work on repositories using this,
@@ -333,31 +323,6 @@ config key: svn.nometadata
-Only used with the 'rebuild' command.
-Run this if you used an old version of git-svn that used
-"git-svn-HEAD" instead of "remotes/git-svn" as the branch
-for tracking the remote.
-Only used with the 'fetch' command.
-By default git-svn will crash if it tries to import a revision
-from SVN which has '(no date)' listed as the date of the revision.
-This is repository corruption on SVN's part, plain and simple.
-But sometimes you really need those revisions anyway.
-If supplied git-svn will convert '(no date)' entries to the UNIX
-epoch (midnight on Jan. 1, 1970). Yes, that's probably very wrong.
-SVN was very wrong.
Basic Examples