From owner-freebsd-hackers Tue Jan 26 09:23:49 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA03310 for freebsd-hackers-outgoing; Tue, 26 Jan 1999 09:23:49 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA03302 for ; Tue, 26 Jan 1999 09:23:47 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id JAA19851; Tue, 26 Jan 1999 09:23:41 -0800 (PST) (envelope-from dillon) Date: Tue, 26 Jan 1999 09:23:41 -0800 (PST) From: Matthew Dillon Message-Id: <199901261723.JAA19851@apollo.backplane.com> To: "Daniel C. Sobral" Cc: hackers@FreeBSD.ORG Subject: Re: 'cpdup' program, and question References: <20657.917338610@zippy.cdrom.com> <199901260830.AAA14635@apollo.backplane.com> <36ADAA43.4B383143@newsguy.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :Does it support command-line passed "ignore" files, instead of :.cpignore? (I prefer to have all these things in one place...) If you mean can you have a single ignore file containing the relative or full paths of the files/directories to ignore, the answer is not at the moment. I see the utility, but it would also be extremely dangerous. You can change the cpignore filename that cpdup looks for in each directory, though. Having .cpignore files in the source directories directly is a safety mechanism. At BEST we even 'chflags schg .cpignore' the most critical files. It may not be necessary for me to be that paranoid now that deletions are confirmed by default ( they aren't in the version BEST was using ). :Does it support patterns in .cpignore? Simple */? patterns. *NOT* regex. :-- :Daniel C. Sobral (8-DCS) :dcs@newsguy.com -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message