From 4ddafa9af1381c3b490f3c52cb1f110bd72d629f Mon Sep 17 00:00:00 2001
From: cperciva <cperciva@FreeBSD.org>
Date: Fri, 28 Dec 2007 20:39:18 +0000
Subject: Attempt to reduce the rate of foot-shooting injuries by adding a new
 paragraph clarifying that portsnap does not behave the same way as cvs and
 cvsup where local modifications are concerned.

Submitted by:	peter
Feet shot:	peter, kris, obrien, + many others
---
 usr.sbin/portsnap/portsnap/portsnap.8 | 9 +++++++++
 1 file changed, 9 insertions(+)

(limited to 'usr.sbin')

diff --git a/usr.sbin/portsnap/portsnap/portsnap.8 b/usr.sbin/portsnap/portsnap/portsnap.8
index 1d7a82b..9fe2dc7 100644
--- a/usr.sbin/portsnap/portsnap/portsnap.8
+++ b/usr.sbin/portsnap/portsnap/portsnap.8
@@ -50,6 +50,15 @@ of the
 .Fx
 ports tree, and extract and update an
 uncompressed ports tree.
+.Pp
+In a normal update operation,
+.Nm
+will routinely restore modified files to their unmodified state and
+delete unrecognized local files.
+This behavior is different to
+.Xr cvs 1
+and
+.Xr cvsup 1 .
 .Sh OPTIONS
 The following options are supported:
 .Bl -tag -width "-f conffile"
-- 
cgit v1.1