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:04:36 -0400 [thread overview]
Message-ID: <h2o3abd05a91004211504pfc2de8b7sa37c9c0a4dd14f57@mail.gmail.com> (raw)
In-Reply-To: <vpqsk6omppf.fsf@bauges.imag.fr>
>
>>> When you do this you're telling git "I want a new branch from where I
>>> am right now". If you want to be able to pull in a similar way to how
>>> master works, use the '--track' option.
>>
>> Actually, the '--track' option is exactly what I don't want ! :) It
>> tells me:
>
> Read the doc. It is what you want, but you mis-use it.
I will read the doc, thank you for the advice.
'When creating a new branch, set up configuration to mark the start-point
branch as "upstream" from the new branch.'
So no, that's not what I want.
Using :
git branch test
git checkout test
git pull origin HEAD
Is what I want and it works. BUT, I used to need only 'git pull'
Again, the behavior changed since I last used this. No one cares?
-- aghiles
next prev parent reply other threads:[~2010-04-21 22:05 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 [this message]
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
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=h2o3abd05a91004211504pfc2de8b7sa37c9c0a4dd14f57@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).