From: Jeff King <peff@peff.net>
To: Maaartin-1 <grajcar1@seznam.cz>
Cc: git@vger.kernel.org
Subject: Re: Tracking branches and pulling on remote
Date: Wed, 5 Jan 2011 11:44:16 -0500 [thread overview]
Message-ID: <20110105164416.GA4393@sigill.intra.peff.net> (raw)
In-Reply-To: <4D249EFA.5050408@seznam.cz>
On Wed, Jan 05, 2011 at 05:40:26PM +0100, Maaartin-1 wrote:
> > $ git config remote.origin.fetch
> > +refs/heads/*:refs/remotes/origin/*
> >
> > which is a superset of what you added. If you run the git config command
> > I did above, what do you see?
>
> No, there had been just the single line
>
> refs/heads/master:refs/remotes/origin/master
Ah, OK, then that is the culprit. And the config line you added was a
reasonable solution (though you may consider simply switching it to a
wildcard to cover any future branches, too).
> OK, I swapped origin and upstream and made aliases
> fetchboth = !"git fetch; git fetch upstream"
> fetup = fetch upstream
> which is about everything I need for now.
Cool. You can also use "git fetch --all" to do the equivalent of your
fetchboth.
-Peff
prev parent reply other threads:[~2011-01-05 16:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-05 0:58 Tracking branches and pulling on remote Maaartin
2011-01-05 5:01 ` Jeff King
2011-01-05 16:40 ` Maaartin-1
2011-01-05 16:44 ` Jeff King [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=20110105164416.GA4393@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=grajcar1@seznam.cz \
/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).