From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16830 invoked by alias); 26 Jul 2007 13:07:24 -0000 Received: (qmail 16731 invoked by uid 22791); 26 Jul 2007 13:07:23 -0000 X-Spam-Check-By: sourceware.org Received: from mx.meyering.net (HELO mx.meyering.net) (82.230.74.64) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 26 Jul 2007 13:07:21 +0000 Received: by rho.meyering.net (Acme Bit-Twister, from userid 1000) id D4BF82CAE9; Thu, 26 Jul 2007 15:07:18 +0200 (CEST) From: Jim Meyering To: overseers@sourceware.org Subject: git repository mirrors? Date: Thu, 26 Jul 2007 13:07:00 -0000 Message-ID: <87ir87e2k9.fsf@rho.meyering.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Mailing-List: contact overseers-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: , Sender: overseers-owner@sourceware.org X-SW-Source: 2007-q3/txt/msg00034.txt.bz2 Hi, This is mostly a heads-up, I suppose. I've begun using the device-mapper and lvm2 repositories recently and find that using them through a git mirror is more effective. So I've set up personal cvs-to-git mirrors that are updated incrementally (efficiently). I plan to publish these read-only repositories on git.et.redhat.com very soon. That's relatively easy for me, because there is already a tried git server configured and running there. And it's easy to keep them up to date. However, if sourceware has such infrastructure already in place (or will soon), it'd make more sense to do it on the system hosting the "upstream" repository. Jim