Re: branch ahead in commits but push claims all up to date
- From
- Santi Béjar <santi@agolina.net>
- Date
- Mar 25, 2009, 17:32 UTC
- Message-ID
- <adf1fd3d0903251032kba19d27gc066b04081a88082@mail.gmail.com>
- In-Reply-To
- <7001b7a00903251023r1ce5cc0dnb29b7f9379408c42@mail.gmail.com>
2009/3/25 Irene Ros <imirene@gmail.com>:
Show 5 quoted lines
> 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).
Show 8 quoted lines
> > 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