From owner-freebsd-current@FreeBSD.ORG Mon Oct 7 23:46:49 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 C9C8156E; Mon, 7 Oct 2013 23:46:49 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7F2512E7C; Mon, 7 Oct 2013 23:46:49 +0000 (UTC) Received: from jre-mbp.elischer.org (ppp121-45-235-45.lns20.per1.internode.on.net [121.45.235.45]) (authenticated bits=0) by vps1.elischer.org (8.14.7/8.14.7) with ESMTP id r97NkiWG034351 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 7 Oct 2013 16:46:46 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <525347DD.5090702@freebsd.org> Date: Tue, 08 Oct 2013 07:46:37 +0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: rcs is gone? References: <29D748F4-5E38-4587-BC7F-0141234C2F62@orthanc.ca> <6CEFF9B8-A62A-4616-A0FF-BDDDE1027A7E@FreeBSD.org> <132C8A43-E822-49C3-A1EA-493A40449AD4@orthanc.ca> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-current@freebsd.org" , Lyndon Nerenberg 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 23:46:49 -0000 On 10/8/13 7:37 AM, Adrian Chadd wrote: > Hi! > > Then you and others should stand up and provide feedback like this far, far > earlier in the development process. Adiran this is the first I've heard of removing RCS. I would have screamed about it had I heard anything.. so now that I officially register my request for a backout can we have it back please? > > If everyone who communicates says "x" and no-one says anything about the > other letters "a"->"w", "y", "z", then we as developers don't really have a > good cross-section of what people actually need. > > If you truely are doing things that require this level of service(s), then > I encourage you to contact the FreeBSD Foundation and communicate exactly > what your requirements are and why. They'll be able to steer things. > > Thanks! > > > -adrian > > > > On 7 October 2013 16:00, Lyndon Nerenberg wrote: > >> On 2013-10-07, at 3:45 PM, Lyndon Nerenberg wrote: >> >>> Having RCS in the base system is very useful. We use it to track >> changes to bits of /etc on the machines where we don't do wholesale >> customizations. (Those ones get git, but they also get an install of >> /usr/ports with a fully populated /usr/ports/distfiles.) >> >> To clarify, the git-enabled machines are a small isolated subset of the >> development machines. Then comes the test and q/a environment, where we >> (by contract) roll nothing beyond the base OS and our application software. >> >> There are other development shops dealing with the same restrictions. >> Most of them have to stay quiet about these requirements on account of the >> Homeland Security. They are all getting buggered over by the fallacy that >> everyone has a gigabit ethernet connection permanently wired into their ass >> ... >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >> > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > >