From: Dave Kleikamp <shaggy@linux.vnet.ibm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org
Subject: Re: linux-next: jfs tree unfetchable
Date: Wed, 14 May 2008 02:31:06 +0000 [thread overview]
Message-ID: <1210732266.6212.11.camel@norville.austin.ibm.com> (raw)
In-Reply-To: <20080514105826.11e87263.sfr@canb.auug.org.au>
On Wed, 2008-05-14 at 10:58 +1000, Stephen Rothwell wrote:
> Hi Dave,
>
> Trying to fetch the jfs tree today gets this error:
>
> fatal: git-upload-pack: cannot find object b2e03ca7485cac033a0667d9e45e28d32fdee9a5:
> fatal: The remote end hung up unexpectedly
Yep. I screwed up my tree. It's fixed now.
> So I will be using what I fetched yesterday ...
No problem. Nothing that can't wait another day (or longer).
Thanks,
Shaggy
--
David Kleikamp
IBM Linux Technology Center
next prev parent reply other threads:[~2008-05-14 2:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-14 0:58 linux-next: jfs tree unfetchable Stephen Rothwell
2008-05-14 2:31 ` Dave Kleikamp [this message]
2008-05-14 5:09 ` Stephen Rothwell
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=1210732266.6212.11.camel@norville.austin.ibm.com \
--to=shaggy@linux.vnet.ibm.com \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).