From: Daniel Drake <dsd@gentoo.org>
To: git@vger.kernel.org
Subject: HTTP repo referencing stale heads (can't clone)
Date: Mon, 03 Apr 2006 17:01:48 +0100 [thread overview]
Message-ID: <443146EC.7060704@gentoo.org> (raw)
Hi,
I maintain a small git repo. I upload it over ssh (with git-push) to a
machine where it is distributed over http:
http://dsd.object4.net/git/zd1211.git/
For some reason it is no longer possible to clone this repo over http:
walk 35afe6b3a859242a18812e7485ea8b211e24abaf
walk 93d9a9f469282e1e392c16ce571da4c08805e8bb
error: Couldn't get
http://dsd.object4.net/git/zd1211.git/refs/heads/softmac-old for
heads/softmac-old
The requested URL returned error: 404
error: Could not interpret heads/softmac-old as something to pull
"softmac-old" is an old branch, which I have recently deleted. I deleted
it by removing the .git/refs/heads/softmac-old file, and relying on
git-prune to clear out old objects.
Even on the server-side, there is no obvious reference to this old head:
$ find -name '*softmac*'
$ grep -R softmac *
(no results for either)
"git-fsck-objects" reports nothing, "git-fsck-objects --full" reports:
dangling commit 7cc423c942975005f96f308186537ad6e7808c2e
dangling commit b36378de6231f1b5100b1517b9c8c243a21090fd
I have tried running git-prune and git-update-server-info, but that
doesn't help.
Any ideas? I'm still new to git.
I am running git-1.2.4
Thanks,
Daniel
next reply other threads:[~2006-04-03 15:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-03 16:01 Daniel Drake [this message]
2006-04-03 17:23 ` HTTP repo referencing stale heads (can't clone) Junio C Hamano
2006-04-03 18:09 ` Nick Hengeveld
2006-04-04 7:03 ` Junio C Hamano
2006-04-04 10:00 ` Petr Baudis
2006-04-04 12:10 ` Nick Hengeveld
2006-04-04 15:27 ` Petr Baudis
2006-04-04 17:56 ` Nick Hengeveld
2006-04-03 18:28 ` Daniel Drake
2006-04-04 18:01 ` Nick Hengeveld
2006-04-05 12:23 ` Radoslaw Szkodzinski
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=443146EC.7060704@gentoo.org \
--to=dsd@gentoo.org \
--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.