From: Aghiles <aghilesk@gmail.com>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: Sverre Rabbelier <srabbelier@gmail.com>, git list <git@vger.kernel.org>
Subject: Re: git pull behavior changed?
Date: Wed, 21 Apr 2010 18:41:16 -0400 [thread overview]
Message-ID: <z2t3abd05a91004211541y1c2c5467k5731819da7fe625@mail.gmail.com> (raw)
In-Reply-To: <vpq8w8gjvhn.fsf@bauges.imag.fr>
> Otherwise, --set-upstream may help. But neither will help untill you
> RTFM.
Matthieu, I spend my days reading the git manual and also the source
code, which is not normal IMHO. I always look for examples but in the
case of 'git branch' there is not many that are really useful!
I suggest to add this as an example since it is probably the most common
case (one would expect that a new branch simply mimics the characteristics
of the starting branch, no ?)
git branch --track small_fixes origin
And it does what I want.
Again, the behavior changed: just upgraded to 1.7.0.3, before then I was
doing branches like this:
git checkout -b small_fixes
git pull
>From my point of view, that was neat!
The --track and <start-point>=origin seemed to be implied. I find that this
is a better better default (OR 'git pull' was defaulting to 'git pull
origin HEAD').
As of now, 'git branch x' seem to be of little use without more configuration.
-- aghiles
next prev parent reply other threads:[~2010-04-21 22:41 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 [this message]
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
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=z2t3abd05a91004211541y1c2c5467k5731819da7fe625@mail.gmail.com \
--to=aghilesk@gmail.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--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).