From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13149 invoked by alias); 5 Mar 2009 22:23:02 -0000 Mailing-List: contact archer-help@sourceware.org; run by ezmlm Sender: Precedence: bulk List-Post: List-Help: List-Subscribe: List-Id: Mail-Followup-To: archer@sourceware.org Received: (qmail 13138 invoked by uid 22791); 5 Mar 2009 22:23:01 -0000 X-SWARE-Spam-Status: No, hits=-1.7 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: Roland McGrath To: Thiago Jung Bauermann Cc: archer ml Subject: Re: git tip In-Reply-To: Thiago Jung Bauermann's message of Thursday, 5 March 2009 19:10:31 -0300 <1236291031.28372.44.camel@localhost.localdomain> References: <1236291031.28372.44.camel@localhost.localdomain> Message-Id: <20090305222231.C83A0FC3BF@magilla.sf.frob.com> Date: Thu, 05 Mar 2009 22:23:00 -0000 X-SW-Source: 2009-q1/txt/msg00342.txt.bz2 > I don't know yet if you can add multiple push entries in .git/config to > create multiple branch mappings, but perhaps you can. You can, and they can have *s in them. Also a leading + implies "-f" behavior, which is usually what you want for branches that only you push to (so you can correct snafus without polluting history). See 'man git-push' for all the details. e.g., this: push = +refs/heads/*:refs/heads/* push = +refs/tags/*:refs/tags/* is what I use in some checkouts where the only local branches I have are ones that I publish in the given remote repo. (You can also use just 'git push repo', e.g. 'git push origin' when you have a checkout tracking multiple published repos that you might push to. i.e., select the repo and let it default the refspec from .git/config.) Thanks, Roland