From: Jan Niklas Hasse <jhasse@gmail.com>
To: Tay Ray Chuan <rctay89@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Error on push (unable to create temporary sha1 filename)
Date: Sat, 27 Feb 2010 13:38:57 +0100 [thread overview]
Message-ID: <8dacd7b31002270438ve59e43djd44e2866b697d3ab@mail.gmail.com> (raw)
In-Reply-To: <be6fef0d1002231654r4fe08149qa937bbd9cc83d6a2@mail.gmail.com>
Hi,
On Wed, Feb 24, 2010 at 1:54 AM, Tay Ray Chuan <rctay89@gmail.com> wrote:
> could you try running "git gc"? Perhaps you have temp files from
> previously aborted/failed pushes lying around.
The output of git gc looks like this:
Counting objects: 102, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (52/52), done.
Writing objects: 100% (102/102), done.
Total 102 (delta 34), reused 102 (delta 34)
But still the same error message when trying to push :(
next prev parent reply other threads:[~2010-02-27 12:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-23 21:11 Error on push (unable to create temporary sha1 filename) Jan Niklas Hasse
2010-02-24 0:54 ` Tay Ray Chuan
2010-02-27 12:38 ` Jan Niklas Hasse [this message]
2010-02-27 13:01 ` Tay Ray Chuan
2010-02-27 13:16 ` Jan Niklas Hasse
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=8dacd7b31002270438ve59e43djd44e2866b697d3ab@mail.gmail.com \
--to=jhasse@gmail.com \
--cc=git@vger.kernel.org \
--cc=rctay89@gmail.com \
/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).