path: root/Documentation/git-svn.txt
diff options
authorShawn Pearce <>2006-09-25 02:50:15 (GMT)
committerJunio C Hamano <>2006-09-25 03:19:22 (GMT)
commitf7bae37f9ab2fdc567780d23495733c9af526e02 (patch)
tree67d5a6111bb3366d956be95f0f608362a55b1e52 /Documentation/git-svn.txt
parent2f60e4e9c18c4cbe1ceacad1bb975a6206ec0411 (diff)
Allow 'svn fetch' on '(no date)' revisions in Subversion.
Added --ignore-nodate to allow 'git svn fetch' to import revisions from Subversion which have '(no date)' listed as the date of the revision. By default 'git svn fetch' will crash with an error when encountering such a revision. The user may restart the fetch operation by adding --ignore-nodate if they want to continue tracking that repository. I'm not entirely sure why a centralized version control system such as Subversion permits revisions to be created with absolutely no date/time associated with it but it apparently is possible as one of the Subversion repositories that I'm tracking with 'git svn' created such a revision on '(no date)' and by '(no user)'. Signed-off-by: Shawn O. Pearce <> Signed-off-by: Junio C Hamano <>
Diffstat (limited to 'Documentation/git-svn.txt')
1 files changed, 12 insertions, 0 deletions
diff --git a/Documentation/git-svn.txt b/Documentation/git-svn.txt
index b7b63f7..1cfa3e3 100644
--- a/Documentation/git-svn.txt
+++ b/Documentation/git-svn.txt
@@ -244,6 +244,18 @@ doing.
repo-config key: svn.noignoreexternals
+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