From: sean <seanlkml@sympatico.ca>
To: "Aneesh Kumar" <aneesh.kumar@gmail.com>
Cc: git@vger.kernel.org, junkio@cox.net
Subject: Re: git pull origin doesn't update the master
Date: Mon, 10 Apr 2006 01:03:16 -0400 [thread overview]
Message-ID: <BAYC1-PASMTP11D3D1D967525A6F029F85AECC0@CEZ.ICE> (raw)
Message-ID: <20060410010316.2aec94ae.seanlkml@sympatico.ca> (raw)
In-Reply-To: <cc723f590604092141q3517136cmc0a895a069021b8f@mail.gmail.com>
On Mon, 10 Apr 2006 10:11:05 +0530
"Aneesh Kumar" <aneesh.kumar@gmail.com> wrote:
> While updating the git code base the master branch is not getting
> updated. First look tell me that the below commit is the issue
> a9698bb22fb7b66e5882c3a5e7b2b8b53ea03f90
>
> git-pull.sh does
> git-fetch --update-head-ok "$@" || exit 1
>
> and git-fetch.sh exit with status 1 printing the below message
>
> * refs/heads/pu: does not fast forward to branch 'pu' of
> http://git.kernel.org/pub/scm/git/git;
> not updating.
>
The "pu" branch often won't fast forward because some commits have
been completely deleted in it since the last time you pulled.
If you want to track it, add a plus (+) sign to the proper line in
your .git/remotes/origin file, like this:
Pull: +refs/heads/pu:refs/heads/pu
Which tells git to deal with the problem for you by merging instead
of fast forwarding. Or you can just delete that line completely
if you don't want to track the pu branch at all.
HTH,
Sean
next prev parent reply other threads:[~2006-04-10 5:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-10 4:41 git pull origin doesn't update the master Aneesh Kumar
2006-04-10 4:51 ` Aneesh Kumar
[not found] ` <20060410010316.2aec94ae.seanlkml@sympatico.ca>
2006-04-10 5:03 ` sean [this message]
2006-04-10 6:29 ` Junio C Hamano
2006-04-10 6:45 ` Aneesh Kumar
2006-04-10 7:24 ` Junio C Hamano
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=BAYC1-PASMTP11D3D1D967525A6F029F85AECC0@CEZ.ICE \
--to=seanlkml@sympatico.ca \
--cc=aneesh.kumar@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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