From owner-freebsd-stable@FreeBSD.ORG Mon Jan 28 14:18:39 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 8D435441 for ; Mon, 28 Jan 2013 14:18:39 +0000 (UTC) (envelope-from ike@blackskyresearch.net) Received: from rs149.luxsci.com (rs149.luxsci.com [64.49.224.181]) by mx1.freebsd.org (Postfix) with ESMTP id 47D25DCF for ; Mon, 28 Jan 2013 14:18:38 +0000 (UTC) Received: from rs149.luxsci.com (localhost.localdomain [127.0.0.1]) by rs149.luxsci.com (8.14.4/8.13.8) with ESMTP id r0SEIbFL012303; Mon, 28 Jan 2013 09:18:37 -0500 Received: (from root@localhost) by rs149.luxsci.com (8.14.4/8.13.8/Submit) id r0SEI1fx011280; Mon, 28 Jan 2013 14:18:01 GMT Received: (from sender 74627) (rs149.luxsci.com [127.0.0.1]) by LuxSci SP; Mon, 28 Jan 2013 14:18:01 +0000 Subject: Re: svn - but smaller? Content-Type: text/plain; charset=windows-1252 From: "Isaac (.ike) Levy" In-Reply-To: <51068698.1010302@missouri.edu> Date: Mon, 28 Jan 2013 09:17:01 -0500 Content-Transfer-Encoding: quoted-printable References: <20130123144050.GG51786@e-Gitt.NET> <20130124111332.GA29105@server.rulingia.com> <1359343502-3377760.86081485.fr0S3OcBl026861@rs149.luxsci.com> <5105F684.501@missouri.edu> <1359380102-3423267.83606864.fr0SDYbB5022353@rs149.luxsci.com> <51068698.1010302@missouri.edu> To: Stephen Montgomery-Smith X-Lux-Comment: Message r0SEH1A4010109 sent by user #74627 Message-Id: <1359382681-308951.083326822.fr0SEH1A4010109@rs149.luxsci.com> X-Comment: LuxSci SP Message ID - 1359382681-308951.083326822 Cc: freebsd-stable@freebsd.org, Peter Jeremy X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 14:18:39 -0000 On CTM: On Jan 28, 2013, at 9:09 AM, Stephen Montgomery-Smith wrote: >> - I'm wondering if there is a clean/reliable way to pull an index of = the CTM deltas? (This is still very far from the one-liner c[v]sup had = become, it would be great to check for new delta files in a simple = automated manner.) >>=20 >=20 > Not sure what you mean. You can do "ctm -l file-name" and it will = tell > you what files are modified in that delta. And for ports, you have = the > usual "make fetchindex." But that is about it. I'm sorry I wasn't clear enough- I meant: On the FTP server, is there an index of which CTM delta files are on the = FTP server? I'd like to automate fetching just the new deltas... If there was perhaps 1 file with a consistent name, I could fetch that = on a nightly basis and fetch the other CTM files. >> - does CTM go away with the CVS servers, e.g. who/how is it supported = supported and maintained going foreword under SVN? >>=20 >=20 > No. CTM is now completely dependent on svn. I create the CTM deltas = on > a computer owned by the University of Missouri. Cool. Is there any redundancy for this process, for example, deltas being = created out on the east/west mirrors? Perhaps as an SVN post-commit = hook? Best, .ike