This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[PATCH] web pages: rsync.html rsync example should be safer


Christian raises a good point - it's a little too easy for someone
to accidentally delete local files with this example cmd -

> 	rsync --archive --delete --checksum --compress \
> 		--stats rsync://gcc.gnu.org/gcc-cvs .
> 


Here's a patch.  OK?

J

Index: rsync.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/rsync.html,v
retrieving revision 1.3
diff -u -p -r1.3 rsync.html
--- rsync.html	23 Jan 2002 15:42:21 -0000	1.3
+++ rsync.html	2 Dec 2002 20:32:34 -0000
@@ -19,7 +19,7 @@ the burden on the GCC main site, and bro
 <h2>Using rsync</h2>
 
 <p>The GCC repository is available at <code>rsync://gcc.gnu.org/gcc-cvs</code>.
-The whole repository does take over 450M of disk space, 
+The whole repository does take over 950M of disk space, 
 which will take a substantial time to transfer.
 Subsequent synchronisations will be much faster though, as rsync uses
 a smart algorithm to only transfer differences over the network.</p>
@@ -27,7 +27,7 @@ a smart algorithm to only transfer diffe
 <p>Here is how you get a copy of the repository:</p>
 <pre>
  % rsync --archive --delete --checksum --compress \
-         --stats rsync://gcc.gnu.org/gcc-cvs .
+         --stats rsync://gcc.gnu.org/gcc-cvs gcc-cvs
 </pre>
 <p>The same command can be run periodically to synchronize your copy of
 the repository.</p>


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]