Issue #1756 -- import doesn't handle svn:eol-style or svn:keywords
From: Julian Foad <julianfoad_at_btopenworld.com>
Date: 2004-03-09 00:30:09 CET
Candidate for 1.0.1:
* r8839,r8932
I am voting -1 for this, due to the "repair" of line endings. For the other reasons mentioned below I would have voted "-0".
A normal commit, via svn_wc_transmit_text_deltas, does not force repair of inconsistent line endings, but fails with an error. This patch to "import", on the other hand, silently "repairs" inconsistent line endings. I think that is the wrong thing for it to do, as I don't see any reason for it to behave differently from "commit".
This patch is on the fuzzy line between fix and enhancement. Lack of this patch only "allows malformed data" in the same way that any commit does if "svn:eol-style" and "svn:keywords" are not as intended. Behaviour without this patch is to preserve the file contents exactly. For these reasons I don't think there is a strong need to put this patch in 1.0.1.
I have reviewed the code but have not tested it. Of course, it would be nice to see regression tests for it, but I can't insist on that. I hope I can assume the "+1" reviewers tested it :-)
One minor thing I found in review is that, while the patch uses svn_string_create generally to create strings, in one place it was done long-hand. This additional patch tidies it up. but there is certainly no need to back-port this:
Index: subversion/libsvn_client/add.c
I will commit that tidy-up separately. (You know how much I like tidying up. I also know how dangerous it can be.)
- Julian
---------------------------------------------------------------------
|
This is an archived mail posted to the Subversion Dev mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.