From: Hannu Koivisto <azure@iki.fi>
To: git@vger.kernel.org
Subject: Re: Errors when updating an old git.git repository
Date: Tue, 26 Dec 2006 21:22:19 +0200 [thread overview]
Message-ID: <87ac1awjh0.fsf@trews52.bothi.fi> (raw)
In-Reply-To: 8c5c35580612260737vae2669dkac6a81fe863484d4@mail.gmail.com
"Lars Hjemli" <hjemli@gmail.com> writes:
> On 12/26/06, Hannu Koivisto <azure@iki.fi> wrote:
> I guess you have some branch references in the file
> .git/remotes/origin that shouldn't be there, so you can just remove
> the lines that mention 'jc/bind', 'jc/bind-2' and 'gb/diffdelta' from
> that file.
Thanks, but I don't need to fix the repository since a clean clone
works, I just wanted to report it so that git can be fixed, if
possible.
>> * refs/heads/pu: not updating to non-fast forward branch 'pu' of git://git.kernel.org/pub/scm/git/git
>> old...new: 0c9951a...f959571
>
> The pu branch is rebased all the time so it needs a '+' in
> .git/remotes/origin to be automatically updated, like this:
>
> Pull: +pu:pu
>
> (or you can run 'git pull -f' to force the update)
I ran 'git pull -f' and it gave me this:
-------------------------------------------------------------------
remote: Generating pack...
remote: Done counting 293 objects.
remote: Result has 214 objects.
remote: Deltifying 214 objects.
remote: 100% (214/214) done
Unpacking 214 objects
remote: Total 214, written 214 (delta 156), reused 181 (delta 123)
100% (214/214) done
error: no such remote ref refs/heads/jc/bind
error: no such remote ref refs/heads/jc/bind-2
error: no such remote ref refs/heads/gb/diffdelta
* refs/heads/pu: forcing update to non-fast forward branch 'pu' of git://git.kernel.org/pub/scm/git/git
old...new: 0c9951a...f959571
* refs/heads/man: fast forward to branch 'man' of git://git.kernel.org/pub/scm/git/git
old..new: 55beec2..da0e8b5
* refs/heads/todo: fast forward to branch 'todo' of git://git.kernel.org/pub/scm/git/git
old..new: a94df75..32e72b6
* refs/heads/next: fast forward to branch 'next' of git://git.kernel.org/pub/scm/git/git
old..new: 50dae10..9c0d79d
* refs/heads/html: fast forward to branch 'html' of git://git.kernel.org/pub/scm/git/git
old..new: 30e1db1..d793de5
Fetch failure: git://git.kernel.org/pub/scm/git/git.git
Already up-to-date.
-------------------------------------------------------------------
Now further 'git pull's also display "Fetch failure:
git://git.kernel.org/pub/scm/git/git.git". It no longer mentions
the 'pu' branch, though.
--
Hannu
next prev parent reply other threads:[~2006-12-26 19:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-26 14:49 Errors when updating an old git.git repository Hannu Koivisto
2006-12-26 15:37 ` Lars Hjemli
2006-12-26 19:22 ` Hannu Koivisto [this message]
2006-12-26 22:54 ` Johannes Schindelin
2006-12-27 0:22 ` Junio C Hamano
2006-12-27 0:45 ` Hannu Koivisto
2006-12-27 0:58 ` 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=87ac1awjh0.fsf@trews52.bothi.fi \
--to=azure@iki.fi \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.