From: Lorenzo Bettini <bettini@dsi.unifi.it>
To: git@vger.kernel.org
Subject: Re: pushing remote branches
Date: Mon, 16 Nov 2009 16:27:32 +0100 [thread overview]
Message-ID: <hdrr1e$oub$1@ger.gmane.org> (raw)
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
next prev parent reply other threads:[~2009-11-16 15:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-14 23:37 pushing remote branches Lorenzo Bettini
2009-11-15 0:45 ` Sitaram Chamarty
2009-11-15 10:21 ` Lorenzo Bettini
2009-11-15 11:04 ` Sitaram Chamarty
2009-11-16 15:27 ` Lorenzo Bettini [this message]
2009-11-16 20:05 ` Junio C Hamano
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='hdrr1e$oub$1@ger.gmane.org' \
--to=bettini@dsi.unifi.it \
--cc=git@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.