git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Santi Béjar" <santi@agolina.net>
To: Irene Ros <imirene@gmail.com>
Cc: Daniel Barkalow <barkalow@iabervon.org>,
	John Tapsell <johnflux@gmail.com>,
	git@vger.kernel.org
Subject: Re: branch ahead in commits but push claims all up to date
Date: Wed, 25 Mar 2009 18:32:37 +0100	[thread overview]
Message-ID: <adf1fd3d0903251032kba19d27gc066b04081a88082@mail.gmail.com> (raw)
In-Reply-To: <7001b7a00903251023r1ce5cc0dnb29b7f9379408c42@mail.gmail.com>

2009/3/25 Irene Ros <imirene@gmail.com>:
> Hi Daniel,
>
> Thank you for the explanation, doing a git fetch actually did do the
> trick although I still don't quite see the difference between
> git pull origin myBranch

This fetches myBranch from origin, and merges with the current branch.

> and
> git fetch

This fetches and *saves* the configured branches (all by default) from
the configured remote (origin by default).

>
> When I push to origin myBranch it's clear that it actually pushes my
> changes to our remote repository since others can then pull and get
> them. So is it the case that:
>
> git push ==> actual remote repository
> while
> git pull <== local copy of remote repository for this branch ?

I don't know if I understand correctly, but pull always uses the
branches from the remote repository, but depending on how you call it
it will also update the local copy (origin/*).

HTH,
Santi

  reply	other threads:[~2009-03-25 17:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <7001b7a00903240821v2155d234x6a10c80a3e987acb@mail.gmail.com>
2009-03-24 15:22 ` branch ahead in commits but push claims all up to date Irene Ros
2009-03-24 16:12   ` Junio C Hamano
2009-03-24 16:18   ` John Tapsell
2009-03-24 17:13     ` Daniel Barkalow
2009-03-25  0:26       ` John Tapsell
2009-03-25  1:24         ` Daniel Barkalow
2009-03-25  2:01           ` Irene Ros
2009-03-25  2:13             ` John Tapsell
2009-03-25  3:19             ` Daniel Barkalow
2009-03-25 17:23               ` Irene Ros
2009-03-25 17:32                 ` Santi Béjar [this message]
2009-03-26  2:05                 ` John Tapsell
2009-03-26 12:48                   ` Björn Steinbrink

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=adf1fd3d0903251032kba19d27gc066b04081a88082@mail.gmail.com \
    --to=santi@agolina.net \
    --cc=barkalow@iabervon.org \
    --cc=git@vger.kernel.org \
    --cc=imirene@gmail.com \
    --cc=johnflux@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).