Mailing-List: contact infrastructure-dev-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: infrastructure-dev@apache.org
Received-SPF: pass (athena.apache.org: domain of jukka.zitting@gmail.com
 designates 64.233.184.234 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=oQuMuoDmnSJMq6MYjekx8I597oJ2KfFLlVboTPSylZ2bDg+pYZwHsbZMPIf1C75bqqczVdMuJBBjuiSw4LnNqjvyUi0AIlXg0Q+DmRTKp4DNjF4qU9/w4GWM+gtKjvkAXXZQqtWROP0+VWOO5GIqOCVHyRzsjSKvY59SICruUt4=
Message-ID: <510143ac0805021225u35c578demb15fdad24678d067@mail.gmail.com>
Date: Fri, 2 May 2008 22:25:22 +0300
From: "Jukka Zitting" <jukka.zitting@gmail.com>
To: infrastructure-dev@apache.org
Subject: Re: Best Practices so far?
In-Reply-To: <5c902b9e0805021204l100c8038n6728cd4dc5d1dfbd@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <481ACF4C.9040509@gmail.com>
	 <510143ac0805020507m302bcbfcje3d77bf9e6437722@mail.gmail.com>
	 <510143ac0805020739s1f0bc6e4t1fd45e3f563c633@mail.gmail.com>
	 <481B3378.30709@apache.org>
	 <fbdc6a970805020849p523b895dh7dec36211e6d5349@mail.gmail.com>
	 <5c902b9e0805020930l1bace3b3vbe2eaaa55ee4a08e@mail.gmail.com>
	 <1209750754.5614.538.camel@marlow>
	 <5c902b9e0805021143x7c3083cg3be197453b9c994d@mail.gmail.com>
	 <1209754696.5614.556.camel@marlow>
	 <5c902b9e0805021204l100c8038n6728cd4dc5d1dfbd@mail.gmail.com>

Hi,

On Fri, May 2, 2008 at 10:04 PM, Justin Erenkrantz
<justin@erenkrantz.com> wrote:
>  As I've repeatedly stated, a 'zone' does not offer you anything at
>  all.  The fact that you're asking for a zone indicates that you don't
>  understand how git is designed to work.  It is meant that you have a
>  local copy of the entire repository.  Having a remote copy sitting on
>  another server is to defeat the purpose of a dSCM.

The reason the zone idea was raised was to work around the potential
load git-svn would put on the svn server. If we only had a single
git-svn mirror pulling from svn and all other git users pulling from
that mirror, then there would be no need to worry about the load on
svn.

But as discussed, the expectation is that svn.eu.apache.org should be
able to deal also with git-svn load (which, as Santiago mentioned,
might even be less or at least not noticeably higher than that from
normal svn clients), so for now I don't think we need the zone, just
some patience to wait until the current svn server crisis is over.

BR,

Jukka Zitting