From: Andrew Sayers <andrew-git@pileofstuff.org>
To: Git Mailing List <git@vger.kernel.org>
Cc: David Barr <davidbarr@google.com>, Jonathan Nieder <jrnieder@gmail.com>
Subject: [PATCH] Explain how svn-fe parses filenames in SVN dumps
Date: Sat, 14 Apr 2012 18:03:09 +0100 [thread overview]
Message-ID: <4F89ADCD.6000109@pileofstuff.org> (raw)
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@pileofstuff.org>
---
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
next reply other threads:[~2012-04-14 17:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-14 17:03 Andrew Sayers [this message]
2012-04-14 17:14 ` [PATCH] Explain how svn-fe parses filenames in SVN dumps Jonathan Nieder
2012-04-14 17:37 ` Andrew Sayers
2012-04-14 18:13 ` Jonathan Nieder
2012-04-14 18:18 ` Jonathan Nieder
2012-04-14 21:56 ` Andrew Sayers
2012-04-15 5:08 ` Jonathan Nieder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F89ADCD.6000109@pileofstuff.org \
--to=andrew-git@pileofstuff.org \
--cc=davidbarr@google.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).