Re: pushing remote branches
- From
Lorenzo Bettini <bettini@dsi.unifi.it>
- Date
- Nov 15, 2009, 10:21 UTC
- Message-ID
- <hdoko1$s78$1@ger.gmane.org>
- In-Reply-To
- <2e24e5b90911141645n59680856ja21f2f3c7063f7c0@mail.gmail.com>
Sitaram Chamarty wrote:
Show 13 quoted lines
> 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?
Show 5 quoted lines
> >> url = git@... > > This is a shortcut for something like ssh://git@..., which then allows write > also.
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/experimentsinstead 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/experimentsI 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?
thanks in advance Lorenzo
-- Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino ICQ# lbetto, 16080134 (GNU/Linux User # 158233) HOME: http://www.lorenzobettini.it MUSIC: http://www.purplesucker.com http://www.myspace.com/supertrouperabba BLOGS: http://tronprog.blogspot.com http://longlivemusic.blogspot.com http://www.gnu.org/software/src-highlite http://www.gnu.org/software/gengetopt http://www.gnu.org/software/gengen http://doublecpp.sourceforge.net