git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sverre Rabbelier <srabbelier@gmail.com>
To: Aghiles <aghilesk@gmail.com>
Cc: git list <git@vger.kernel.org>
Subject: Re: git pull behavior changed?
Date: Wed, 21 Apr 2010 23:59:05 +0200	[thread overview]
Message-ID: <u2zfabb9a1e1004211459k74c23b56tbd8de958d82f0cca@mail.gmail.com> (raw)
In-Reply-To: <y2p3abd05a91004211455r30d13932t92dfbedff581b9a1@mail.gmail.com>

Heya,

On Wed, Apr 21, 2010 at 23:55, Aghiles <aghilesk@gmail.com> wrote:
> Without the '--track' option it seems to work as expected: when I pull
> it downloads data form the remote but then stops before merging.
> This used to work! What happened ? :(

See the --track documentation, you need to tell it to track upstream
instead of master.

-- 
Cheers,

Sverre Rabbelier

  reply	other threads:[~2010-04-21 21:59 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 [this message]
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
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=u2zfabb9a1e1004211459k74c23b56tbd8de958d82f0cca@mail.gmail.com \
    --to=srabbelier@gmail.com \
    --cc=aghilesk@gmail.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).