The documentation for the SVN dumpfile format says that filenames "may be interpreted as binary data in any encoding by client tools", but users might be surprised that svn-fe's handling differs from svn's. Before version 1.2.0, `svn add` supported files containing characters in the range 0x01-0x1F, and Subversion still supports existing files that contain those characters. The newline character is explicitly discussed so that users with ancient repositories understand why they can't be supported by tools that read the SVN dump format. The documentation for the SVN dumpfile format describes records as containing "a group of RFC822-style header lines", and its full text can be read as implying newline characters are reserved for use by the format. This reading is slightly charitable, but it avoids the need to discuss the format's design issues in a context where few readers will be interested. Signed-off-by: Andrew Sayers <andrew-git@xxxxxxxxxxxxxxx> --- contrib/svn-fe/svn-fe.txt | 8 ++++++++ 1 files changed, 8 insertions(+), 0 deletions(-) diff --git a/contrib/svn-fe/svn-fe.txt b/contrib/svn-fe/svn-fe.txt index 1128ab2..c079abe 100644 --- a/contrib/svn-fe/svn-fe.txt +++ b/contrib/svn-fe/svn-fe.txt @@ -59,6 +59,14 @@ to put each project in its own repository and to separate the history of each branch. The 'git filter-branch --subdirectory-filter' command may be useful for this purpose. +Filenames are interpreted by svn-fe as binary data, and may contain +any character except NUL (0x00) and newline (0x0A). The NUL +character is not valid in git paths, and the newline character is +reserved for use by the (line-based) Subversion dumpfile format. +This differs from Subversion, which requires filenames to contain +only legal XML characters and disallows tabs characters, carriage +returns and newlines. + BUGS ---- Empty directories and unknown properties are silently discarded. -- 1.7.1 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html