From: Jeff King <peff@peff.net>
To: Stephen Bash <bash@genarts.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: git push on tracking branches
Date: Mon, 27 Sep 2010 12:05:48 -0400 [thread overview]
Message-ID: <20100927160548.GA10256@sigill.intra.peff.net> (raw)
In-Reply-To: <15793457.371451.1285603241207.JavaMail.root@mail.hq.genarts.com>
On Mon, Sep 27, 2010 at 12:00:41PM -0400, Stephen Bash wrote:
> A coworker alerted me to some strange behavior with git push on tracking branches (maybe a documentation error?). Pro Git (http://progit.org/book/ch3-5.html) says:
>
> "To set up a local branch with a different name than the remote branch, you can easily use the first version with a different local branch name:
> $ git checkout -b sf origin/serverfix
> Branch sf set up to track remote branch refs/remotes/origin/serverfix.
> Switched to a new branch "sf"
> Now, your local branch sf will automatically push to and pull from origin/serverfix."
That has never been the case by default. Push has always defaulted to
pushing all matching branches (so of course if you use the same name, it
will end up pushing to the tracking branch). However, you can do:
git config --global push.default tracking
to explicitly change the default to push the current branch to its
upstream. See the entry for "push.default" in "git help config".
It may be that Pro Git suggested setting up that config earlier. If not,
you should probably submit a bug report for the book.
-Peff
next prev parent reply other threads:[~2010-09-27 16:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6958088.371432.1285602164529.JavaMail.root@mail.hq.genarts.com>
2010-09-27 16:00 ` git push on tracking branches Stephen Bash
2010-09-27 16:05 ` Jeff King [this message]
2010-09-27 16:14 ` Stephen Bash
2010-09-27 17:16 ` Nick
2010-09-27 17:53 ` Jeff King
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=20100927160548.GA10256@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=bash@genarts.com \
--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).