git pull is actually the same as if you write git fetch and then git merge.
git-fetch doesn't update anything in your working directory, it just download the changes from the remote. Think about it as if I ask you "what did you change in the code?" You tell me, but I don't apply it to my version yet; that's what git-merge is for. Best, Gergely On 24 Jul 2015 09:42, "dexter ietf" <dexter.i...@gmail.com> wrote: > > On Thursday, July 23, 2015 at 8:12:45 PM UTC+5:30, Konstantin Khomoutov > wrote: >> >> On Thu, 23 Jul 2015 06:44:41 -0700 (PDT) >> dexter ietf <dexte...@gmail.com> wrote: >> >> That's almost zero information in your problem statement. >> >> > ok, the remote repo from which i cloned the bare repo has the following > tags: > > tagv10 > tagv9 > tagv8 > tagv7 > .. > tagv1 > > while my repo has only tags starting from tagv7, that was the latest tag > when i cloned the bare repo. > > also the HEAD of the remote repo and my bare repo is pointing at > different commits even after 'git fetch', i was expecting 'git fetch' > is just like 'git pull' on a non-bare repo. what am i missing ..? > > -- > You received this message because you are subscribed to the Google Groups > "Git for human beings" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to git-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
