Got rid of the changes to proto.h and mentioned the build instructions

[rsync/rsync-patches.git] / write-only.diff

diff --git a/write-only.diff b/write-only.diff
index 89ee856..cb617f1 100644 (file)
--- a/write-only.diff
+++ b/write-only.diff
@@ -1,16 +1,15 @@
-From: peter pan <lanwanhr@yahoo.com>
-Subject: [PATCH] write only
-Date: Thu, 12 Feb 2004 04:08:00 -0800 (PST)
+After applying this patch and running configure, you MUST run this
+command before "make":
+
+    make proto
+
+peter pan (lanwanhr@yahoo.com) writes:
 
 I've added a write only option to rsyncd.conf which is essentially the opposite
 of read only.  This means that although it's possible someone on our allowed IP
 range could overwrite (or delete) files on the rsync share, they would not be
 allowed to download any files (my primary concern).
 
-J
-
-[Updated to CVS version by Wayne Davison.]
-
 
 --- loadparm.c 4 Feb 2004 07:31:29 -0000       1.50
 +++ loadparm.c 22 Apr 2004 23:49:29 -0000
@@ -61,13 +60,3 @@ J
        if (!relative_paths && !push_dir(dir)) {
                rprintf(FERROR, "push_dir %s failed: %s (3)\n",
                        full_fname(dir), strerror(errno));
---- proto.h    22 Apr 2004 09:58:09 -0000      1.189
-+++ proto.h    22 Apr 2004 23:49:29 -0000
-@@ -132,6 +132,7 @@ char *lp_comment(int );
- char *lp_path(int );
- char *lp_lock_file(int );
- BOOL lp_read_only(int );
-+BOOL lp_write_only(int );
- BOOL lp_list(int );
- BOOL lp_use_chroot(int );
- BOOL lp_transfer_logging(int );