From: Linus Torvalds <torvalds@linux-foundation.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] GIT 1.5.1.2
Date: Sun, 22 Apr 2007 10:22:47 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.0.98.0704221019100.9964@woody.linux-foundation.org> (raw)
In-Reply-To: <7v1widrl0o.fsf@assigned-by-dhcp.cox.net>
On Sat, 21 Apr 2007, Junio C Hamano wrote:
>
> The latest maintenance release GIT 1.5.1.2 is available at the
> usual places:
Well, by "available" you probably mean "not available", because it doesn't
actually work.
I get EPERM on pack-e00affefe0f779d0f9b0507aef25a1733f4a9117.idx/pack,
because they are
-r-------- 1 junio junio 1120880
-r-------- 1 junio junio 15709370
respectively.
As a result, nothing really works, ie:
[torvalds@hera git.git]$ git log
error: Could not read 42c4b58059fa9af65e90f2c418bb551e30d1d32f
and doing a "git pull" will just result in lots of
error: refs/heads/maint does not point to a valid object!
error: refs/heads/next does not point to a valid object!
error: refs/heads/todo does not point to a valid object!
...
which is perhaps a bit of a misleading error message (technically true,
but ..)
Oops.
Linus
next prev parent reply other threads:[~2007-04-22 17:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-12 2:09 [ANNOUNCE] GIT 1.5.1.1 Junio C Hamano
2007-04-22 6:16 ` [ANNOUNCE] GIT 1.5.1.2 Junio C Hamano
2007-04-22 17:22 ` Linus Torvalds [this message]
2007-04-22 17:58 ` Junio C Hamano
2007-04-22 18:06 ` Today's 'master' leaves .idx/.pack in 0400 Junio C Hamano
2007-04-22 18:25 ` Nicolas Pitre
2007-04-22 18:27 ` Junio C Hamano
2007-04-22 18:34 ` Nicolas Pitre
2007-04-22 18:47 ` Nicolas Pitre
2007-04-22 18:52 ` Junio C Hamano
2007-04-22 18:54 ` Linus Torvalds
2007-04-22 19:03 ` Junio C Hamano
2007-04-22 19:20 ` Junio C Hamano
2007-04-22 19:29 ` Linus Torvalds
2007-04-22 18:47 ` [ANNOUNCE] GIT 1.5.1.2 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=alpine.LFD.0.98.0704221019100.9964@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®