From: Aghiles <aghilesk@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>,
Sverre Rabbelier <srabbelier@gmail.com>,
git list <git@vger.kernel.org>
Subject: Re: git pull behavior changed?
Date: Wed, 21 Apr 2010 21:27:31 -0400 [thread overview]
Message-ID: <v2z3abd05a91004211827ua3955912w676d8a3e001ed461@mail.gmail.com> (raw)
In-Reply-To: <20100422004136.GA18570@coredump.intra.peff.net>
> OK, then the behavior did change for you. But you are probably about 3
> years too late to complain and try to get it changed. :)
Dammit. :) But really no biggie. I just entered panic mode because I
thought something got borked in my favorite tool, which is not the case
obviously.
> You may also be interested to know that "git checkout foo" these days
> when you have no "foo" branch will do the equivalent of "git checkout -b
> --track foo origin/foo", which would also do what you want.
Wouldn't that create/track a remote 'foo' branch ? I have no remote branches
but only local ones so I am always tracking origin/master.
-- aghiles
next prev parent reply other threads:[~2010-04-22 1:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-21 21:13 git pull behavior changed? Aghiles
2010-04-21 21:22 ` Sverre Rabbelier
2010-04-21 21:34 ` Aghiles
2010-04-21 21:55 ` Aghiles
2010-04-21 21:59 ` Sverre Rabbelier
2010-04-21 21:59 ` Matthieu Moy
2010-04-21 22:04 ` Aghiles
2010-04-21 22:23 ` Matthieu Moy
2010-04-21 22:41 ` Aghiles
2010-04-22 0:01 ` Jeff King
2010-04-22 0:13 ` Aghiles
2010-04-22 0:41 ` Jeff King
2010-04-22 1:27 ` Aghiles [this message]
2010-04-22 2:10 ` Jeff King
2010-04-21 23:27 ` Randal L. Schwartz
2010-04-21 23:57 ` Aghiles
2010-04-22 8:10 ` Petr Baudis
2010-04-22 8:16 ` Junio C Hamano
2010-04-22 11:49 ` Creating tracked branches Petr Baudis
2010-04-22 13:47 ` Andreas Schwab
2010-04-22 14:17 ` Petr Baudis
2010-04-22 21:13 ` git pull behavior changed? Aghiles
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=v2z3abd05a91004211827ua3955912w676d8a3e001ed461@mail.gmail.com \
--to=aghilesk@gmail.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=srabbelier@gmail.com \
/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).