Re: Excluding some refspecs from git push?

From: Magnus Bäck <magnus.back@sonyericsson.com>
Date: Jul 24, 2011, 19:32 UTC
Message-ID: <20110724193240.GA16283@jpl.local>
In-Reply-To: <CAH+XAApbbMSPW9XJPjYnmqNiECoWBz5du6CeD_hfAww9o_LcXA@mail.gmail.com>

On Sunday, July 24, 2011 at 21:19 CEST,
     Shawn Pearce <sop@google.com> wrote:

Show 19 quoted lines

> On Sat, Jul 23, 2011 at 14:46, Paul Sokolovsky
> <paul.sokolovsky@linaro.org> wrote:
> > Is there a way to exclude some refspec from being processed by "git
> > push"? What I'm looking for is a syntax like:
> >
> > push some-remote 'refs/*' '!refs/meta/config'
> >
> > , with the meaning of "push all refs except refs/meta/config". What
> > I'm trying to do with this is to find out a generic way to mirror
> > git repositories managed by the Gerrit tool
> > (http://code.google.com/p/gerrit/), which since version 2.2 uses
> > refs/meta/config branch to store repository-local configuration, so
> > should not be mirrored between two Gerrit's.
> 
> Unfortunately no. But you should be able to just mirror the namespaces
> that matter:
> 
>   refs/heads/*
>   refs/tags/*

Any reason to omit refs/notes/*?

> Its not a good idea to mirror refs/meta/config unless you want the
> same access controls, *AND ITS REALLY NOT A GOOD IDEA TO MIRROR
> refs/changes/* BETWEEN GERRIT SERVERS*. Yes, that last part is worth
> writing in full caps.

Because of the excessive number of refs to advertise for a non-Gerrit server, or what's the reason for the full caps?

-- 
Magnus Bäck                   Opinions are my own and do not necessarily
SW Configuration Manager      represent the ones of my employer, etc.
Sony Ericsson