From: "Magnus Bäck" <magnus.back@sonyericsson.com>
To: Shawn Pearce <sop@google.com>
Cc: Paul Sokolovsky <paul.sokolovsky@linaro.org>,
git@vger.kernel.org, repo-discuss <repo-discuss@googlegroups.com>
Subject: Re: Excluding some refspecs from git push?
Date: Sun, 24 Jul 2011 21:32:40 +0200 [thread overview]
Message-ID: <20110724193240.GA16283@jpl.local> (raw)
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:
> 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
next prev parent reply other threads:[~2011-07-24 19:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-23 21:46 Excluding some refspecs from git push? Paul Sokolovsky
2011-07-24 19:19 ` Shawn Pearce
2011-07-24 19:32 ` Magnus Bäck [this message]
2011-07-24 19:45 ` Shawn Pearce
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110724193240.GA16283@jpl.local \
--to=magnus.back@sonyericsson.com \
--cc=git@vger.kernel.org \
--cc=paul.sokolovsky@linaro.org \
--cc=repo-discuss@googlegroups.com \
--cc=sop@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).