Subject: Re: Overriding ~/.gitconfig using GIT_CONFIG

From: Richard Purdie <[email-masked]>
Date: Tue, 30 Aug 2011 19:39:05 +0100

On Tue, 2011-08-30 at 11:56 -0400, Jeff King wrote:
> 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?

Since this is a bare/mirror clone, wouldn't that need to be:

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

?

That also wouldn't fetch tags?

Cheers,

Richard