From: Pavel Roskin <proski@gnu.org>
To: git <git@vger.kernel.org>
Subject: What's wrong with cogito repository today?
Date: Tue, 20 Sep 2005 12:27:13 -0400 [thread overview]
Message-ID: <1127233633.8374.26.camel@dv> (raw)
Hello!
cogito repository is broken today:
$ git-fetch
Fetching refs/heads/master from http://www.kernel.org/pub/scm/cogito/cogito.git/ using http
Getting pack list
Getting alternates list
error: Unable to find 69ba00668be16e44cae699098694286f703ec61d under http://www.kernel.org/pub/scm/cogito/cogito.git//
Cannot obtain needed object 69ba00668be16e44cae699098694286f703ec61d
while processing commit 0000000000000000000000000000000000000000.
[proski@dv cogito]$ curl http://www.kernel.org/pub/scm/cogito/cogito.git/refs/heads/master
69ba00668be16e44cae699098694286f703ec61d
[proski@dv cogito]$ wget http://www.kernel.org/pub/scm/cogito/cogito.git/objects/69/ba00668be16e44cae699098694286f703ec61d
--12:19:49-- http://www.kernel.org/pub/scm/cogito/cogito.git/objects/69/ba00668be16e44cae699098694286f703ec61d
=> `ba00668be16e44cae699098694286f703ec61d'
Resolving www.kernel.org... 204.152.191.5
Connecting to www.kernel.org[204.152.191.5]:80... connected.
HTTP request sent, awaiting response... 404 Not Found
12:19:49 ERROR 404: Not Found.
I don't know how the commits are pushed to kernel.org, but maybe it's
possible to prevent such breakage by ensuring that the head is only
updated if the objects have been uploaded?
--
Regards,
Pavel Roskin
next prev reply other threads:[~2005-09-20 16:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-20 18:23 "git pull" on cogito broken? Randal L. Schwartz
2005-09-20 16:27 ` Pavel Roskin [this message]
2005-09-20 19:05 ` What's wrong with cogito repository today? Petr Baudis
2005-09-20 18:41 ` "git pull" on cogito broken? Stefhen Hovland
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=1127233633.8374.26.camel@dv \
--to=proski@gnu.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.