From: Lorenzo Bettini Date: Mon, 16 Nov 2009 15:27:32 GMT Subject: Re: pushing remote branches Message-ID: In-Reply-To: <2e24e5b90911150304i1472ed13k6c60611ef2e9ba19@mail.gmail.com> Sitaram Chamarty wrote: > >> Thus, if I had >> >> [remote "origin"] >> fetch = +refs/heads/*:refs/remotes/origin/* >> url = git@... >> [branch "master"] >> remote = origin >> merge = refs/heads/master >> [branch "experiments"] >> remote = origin >> merge = refs/heads/experiments >> >> instead of >> >> [remote "origin"] >> fetch = +refs/heads/*:refs/remotes/origin/* >> url = git://... >> [branch "master"] >> remote = origin >> merge = refs/heads/master >> [branch "experiments"] >> remote = origin >> merge = refs/heads/experiments >> >> I would have been able to push also to branch experiments? Without having >> to add >> >> [remote "experiments"] >> url = git@... >> fetch = +refs/heads/experiments:refs/remotes/experiments/experiments >> >> ? > > (by the way: do you mean refs/remotes/origin/experiments in that last > line above?) > no, it's just like I wrote it... you mean in [remote "experiments"] url = git@gitorious.org... fetch = +refs/heads/experiments:refs/remotes/experiments/experiments or in [branch "experiments"] remote = origin merge = refs/heads/experiments ? > Anyway to answer your question, I do not see the refspec line as the issue > here, but the URL for the repo, which determines how you access it. so this would have been enough: >> [remote "origin"] >> fetch = +refs/heads/*:refs/remotes/origin/* >> url = git://... >> [branch "master"] >> remote = origin >> merge = refs/heads/master >> [branch "experiments"] >> remote = origin >> merge = refs/heads/experiments ? thanks Lorenzo -- Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino HOME: http://www.lorenzobettini.it MUSIC: http://www.purplesucker.com BLOGS: http://tronprog.blogspot.com http://longlivemusic.blogspot.com