Author: stsp
Date: Fri Aug 18 11:48:53 2017
New Revision: 1805403
URL: http://svn.apache.org/viewvc?rev=1805403&view=rev
Log:
* publish/faq.html
(dumpload): Highlight property names in the 2 dump error messages to
make their difference stand out more. Fix a wording ambiguity.
Modified:
subversion/site/publish/faq.html
Modified: subversion/site/publish/faq.html
URL:
http://svn.apache.org/viewvc/subversion/site/publish/faq.html?rev=1805403&r1=1805402&r2=1805403&view=diff
==============================================================================
--- subversion/site/publish/faq.html (original)
+++ subversion/site/publish/faq.html Fri Aug 18 11:48:53 2017
@@ -1582,7 +1582,7 @@ afterwards (for instance using 'svnlook
svnadmin: E125005: Invalid property value found in dumpstream; consider
repairing the
source or using --bypass-prop-validation while loading.
-svnadmin: E125005: Cannot accept non-LF line endings in 'svn:log' property
+svnadmin: E125005: Cannot accept non-LF line endings in '<b>svn:log</b>'
property
</pre>
This means the svn:log message of the revision has non-LF line endings (these
@@ -1601,11 +1601,11 @@ it can easily be fixed without "rewritin
svnadmin: E125005: Invalid property value found in dumpstream; consider
repairing the
source or using --bypass-prop-validation while loading.
-svnadmin: E125005: Cannot accept non-LF line endings in 'svn:ignore' property
+svnadmin: E125005: Cannot accept non-LF line endings in '<b>svn:ignore</b>'
property
</pre>
This is more difficult to repair, because 'svn:ignore' is not a
-revision property (like svn:log, which can be manipulated with
+revision property (unlike svn:log, which can be manipulated with
svnadmin setrevprop), but a <i>versioned property</i> (so it's part of
history). Again, you can ignore this with --bypass-prop-validation.
But since this is a corruption "in history", this can only be repaired
