From: "Alex Riesen" <raa.lkml@gmail.com>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: Many different remote branch sources
Date: Fri, 2 Mar 2007 23:18:36 +0100 [thread overview]
Message-ID: <81b0412b0703021418y6ff084d1r9eaf72aeac4eb51@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0703021645200.22628@wbgn013.biozentrum.uni-wuerzburg.de>
On 3/2/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> Rather, add a "fetch = refs/heads/topic1" at the _top_ of the remotes.dev1
> section, and say "git pull dev1" when you want to pull from dev1.
This is exactly what I wanted. I just somehow believed that
git pull uses only references configured in branch sections,
never the references in "remote" sections. Am a bit confused.
prev parent reply other threads:[~2007-03-02 22:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-02 10:53 Many different remote branch sources Alex Riesen
2007-03-02 15:47 ` Johannes Schindelin
2007-03-02 22:18 ` Alex Riesen [this message]
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=81b0412b0703021418y6ff084d1r9eaf72aeac4eb51@mail.gmail.com \
--to=raa.lkml@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).