From owner-freebsd-current@FreeBSD.ORG Thu Oct 10 20:35:38 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 34011C03 for ; Thu, 10 Oct 2013 20:35:38 +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 D1E5F2B2E for ; Thu, 10 Oct 2013 20:35:37 +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.7/8.14.7) with ESMTP id r9AKZYPK011260 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Thu, 10 Oct 2013 13:35:35 -0700 (PDT) (envelope-from lyndon@orthanc.ca) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Subject: Re: rcs From: Lyndon Nerenberg In-Reply-To: Date: Thu, 10 Oct 2013 13:35:33 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <97203F19-A5F5-40A9-9DEE-C73C8C9F51CB@orthanc.ca> References: <77307DF8-637D-4295-BF47-8742F1552CE8@orthanc.ca> <525503A2.50002@beastielabs.net> <525537F5.1050100@m5p.com> <5256D192.8010902@freebsd.org> <5256D819.6060500@freebsd.org> To: "freebsd-current@freebsd.org" 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: Thu, 10 Oct 2013 20:35:38 -0000 On 2013-10-10, at 1:06 PM, Igor Mozolevsky = wrote: > You're missing the point- the requirement is "provide a way to keep = track > of changes for file X" not "have many fancy and unnecessary = features"... The point is to put back the specific RCS commands that were recently = removed. Those of us using RCS do so because it's in the base system. If we = wanted/needed another SCM, we would install it from ports. But many of = us use RCS specifically because installing a port is not an option. = *Why* it's not an option is not relevant. RCS is not broken, and is very low maintenance code. = /usr/src/gnu/usr.bin/rcs has been modified four times in the last = decade. Two of those changes were sweeping Makefile updates that = affected much more than RCS. Of the other two, only one update touched = the actual code, and that was a one line change to a .h. --lyndon