From: Jeff King <peff@peff.net>
Date: Tue, 30 Aug 2011 15:56:49 GMT
Subject: Re: Overriding ~/.gitconfig using GIT_CONFIG
Message-ID: <20110830155649.GA15790@sigill.intra.peff.net>
In-Reply-To: <1314706381.5939.348.camel@rex>

On Tue, Aug 30, 2011 at 01:13:01PM +0100, Richard Purdie wrote:

> We've gone through several iterations of this but as things stand now,
> to initially clone things we're doing:
> 
> git clone --bare --mirror <url> <dir>
> 
> but if we already have some existing clone we'd update with:
> 
> git remote prune origin
> git remote rm origin
> git remote add --mirror origin <url>
> git fetch --all -t
>
> [...]
>
> So if a user has an origin remote in their .gitconfig, can we ignore it?

Wouldn't:

  git fetch --prune <url> refs/heads/*:refs/remotes/origin/*

do what you want, and not look at config at all?

-Peff