Re: pushing remote branches
- From
Sitaram Chamarty <sitaramc@gmail.com>
- Date
- Nov 15, 2009, 11:04 UTC
- Message-ID
- <2e24e5b90911150304i1472ed13k6c60611ef2e9ba19@mail.gmail.com>
- In-Reply-To
- <hdoko1$s78$1@ger.gmane.org>
On Sun, Nov 15, 2009 at 3:51 PM, Lorenzo Bettini <bettini@dsi.unifi.it> wrote:
Show 19 quoted lines
> Sitaram Chamarty wrote: >> >> Hi Lorenzo, >> >> On Sun, Nov 15, 2009 at 5:07 AM, Lorenzo Bettini <bettini@dsi.unifi.it> >> wrote: >> >>> url = git://... >> >>> isn't this enough to be able to push the experiments branch? >> >> not normally. >> >> The "git://" protocol is a read-only protocol by default. Since it is >> completely unauthenticated, enabling push via git:// is not a good idea in >> general. > > so probably I managed to push origin master anyway because gitorious asked > me for my ssh passphrase?
As far as I know you could not have pushed anything when the url is git:// (at least by default. Push over git:// can be enabled but is highly inadvisable and I have not seen anyone enable it nor any good reason to)
Show 32 quoted lines
> 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?)
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.
regards,
sitaram