From: Daniel Jacobowitz <drow@false.org>
To: Jim Meyering <jim@meyering.net>
Cc: gdb@sourceware.org
Subject: Re: gdb.git hiccup
Date: Sat, 03 Oct 2009 23:35:00 -0000 [thread overview]
Message-ID: <20091003233527.GA9182@caradoc.them.org> (raw)
In-Reply-To: <87k4zclc87.fsf@meyering.net>
On Sat, Oct 03, 2009 at 05:38:00PM +0200, Jim Meyering wrote:
> FYI, so far, here's all I've done:
>
> head=a4a5c910c73f0bf2b7d063912274461838139423
> git update-ref HEAD $head
> git update-ref master $head
>
> That should be enough for now.
So, this is supposed to be fixed now?
I've been getting this all day:
dan@henry1:/scratch/dan git clone git://sourceware.org/git/archer.git
Initialized empty Git repository in /scratch/dan/archer/.git/
fatal: The remote end hung up unexpectedly
which I assumed was related...
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2009-10-03 23:35 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-03 12:30 Jim Meyering
2009-10-03 13:22 ` Jim Meyering
2009-10-03 15:38 ` Jim Meyering
2009-10-03 17:05 ` Joel Brobecker
2009-10-03 23:35 ` Daniel Jacobowitz [this message]
2009-10-04 6:51 ` Jim Meyering
2009-10-04 11:09 ` Frank Ch. Eigler
2009-10-04 12:15 ` Jim Meyering
2009-10-04 12:40 ` Frank Ch. Eigler
2009-10-04 12:15 ` Matt Rice
2009-10-04 12:43 ` Jim Meyering
[not found] ` <20091004142139.GA19501@host0.dyn.jankratochvil.net>
2009-10-04 20:16 ` Jim Meyering
2009-10-05 1:46 ` Jan Kratochvil
2009-10-05 10:14 ` Jim Meyering
2009-10-06 20:48 ` Jan Kratochvil
2009-10-06 21:12 ` Jim Meyering
2009-10-06 21:23 ` Jim Meyering
2009-10-04 14:49 ` Christopher Faylor
2009-10-04 15:05 ` Jim Meyering
2009-10-04 15:15 ` Christopher Faylor
2009-10-04 20:34 ` Jim Meyering
2009-10-06 22:03 ` Joel Brobecker
2009-10-07 14:52 ` Jim Meyering
[not found] ` <20091007192519.GK16338@adacore.com>
2009-10-07 21:13 ` Jim Meyering
2009-10-08 9:20 ` Jim Meyering
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=20091003233527.GA9182@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=jim@meyering.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