From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 21:02:58 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 1F075FDB for ; Mon, 7 Oct 2013 21:02:58 +0000 (UTC) (envelope-from lyndon@orthanc.ca) Received: from orthanc.ca (orthanc.ca [IPv6:2607:fc50:1000:8200::42]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id BDFC9236F for ; Mon, 7 Oct 2013 21:02:57 +0000 (UTC) Received: from [192.168.42.129] (d66-183-220-167.bchsia.telus.net [66.183.220.167] (may be forged)) (authenticated bits=0) by orthanc.ca (8.14.6/8.14.6) with ESMTP id r97L2sCu024825 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Mon, 7 Oct 2013 14:02:56 -0700 (PDT) (envelope-from lyndon@orthanc.ca) From: Lyndon Nerenberg Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: rcs is gone? Message-Id: <29D748F4-5E38-4587-BC7F-0141234C2F62@orthanc.ca> Date: Mon, 7 Oct 2013 14:02:50 -0700 To: "freebsd-current@freebsd.org" Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) X-Mailer: Apple Mail (2.1510) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2013 21:02:58 -0000 I know I am a certified crank, but ... why? This is some of the = simplest code on the planet. Is it broken by recent OS releases? I use = ci/co every single day to track changes to individual config files on = individual machines. For simple things like ntp.conf, rc.conf, = sysctl.conf, a simple 'ci -l xxx' is a trivial way to maintain local = revision control. For small stand-alone systems, RCS is more than adequate. Why ditch it? --lyndon