svn commit: r1436328 - /subversion/trunk/subversion/libsvn_client/patch.c

[st...@apache.org]

Author: stsp
Date: Mon Jan 21 13:03:00 2013
New Revision: 1436328

URL: http://svn.apache.org/viewvc?rev=1436328&view=rev
Log:
* subversion/libsvn_client/patch.c: In the comment talking about symlinks,
   explain the "normal form" of symlinks just once, not twice.

Modified:
    subversion/trunk/subversion/libsvn_client/patch.c

Modified: subversion/trunk/subversion/libsvn_client/patch.c
URL: http://svn.apache.org/viewvc/subversion/trunk/subversion/libsvn_client/patch.c?rev=1436328&r1=1436327&r2=1436328&view=diff
==============================================================================
--- subversion/trunk/subversion/libsvn_client/patch.c (original)
+++ subversion/trunk/subversion/libsvn_client/patch.c Mon Jan 21 13:03:00 2013
@@ -806,13 +806,13 @@ write_file(void *baton, const char *buf,
  * In Subversion, symlinks can be represented on disk in two distinct ways.
  * On systems which support symlinks, a symlink is created on disk.
  * On systems which do not support symlink, a file is created on disk
- * which contains "link TARGET" where TARGET is the file the symlink
- * points to.
+ * which contains the "normal form" of the symlink, which looks like:
+ *   link TARGET
+ * where TARGET is the file the symlink points to.
  *
  * When reading symlinks (i.e. the link itself, not the file the symlink
  * is pointing to) through the svn_subst_create_specialfile() function
- * into a buffer, the buffer always contains the "normal form" of the symlink,
- * which looks like: "link TARGET"
+ * into a buffer, the buffer always contains the "normal form" of the symlink.
  * Due to this representation symlinks always contain a single line of text.
  *
  * The functions below are needed to deal with the case where a patch