From: Jerry Van Baren <vanbargw@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Oh-oh out of disk space on the server
Date: Thu, 16 Aug 2007 22:21:16 -0400 [thread overview]
Message-ID: <46C5061C.5040208@gmail.com> (raw)
Hi Wolfgang,
I applied Kim's patch of Aug 10 and tried to push it but received a "no
space left on device" error. Help!
Thanks,
gvb
$ git push git+ssh://gu-fdt at www.denx.de/u-boot-fdt fdt
updating 'refs/heads/fdt'
from 308e2b3a6c3fd84fceada79b3d4a559280d326a6
to 8f8aa4d0e7d37eb2cfef054d0bc5736d20b99657
Generating pack...
Done counting 49 objects.
Result has 25 objects.
Deltifying 25 objects.
100% (25/25) done
Writing 25 objects.
100% (25/25) done
Total 25, written 25 (delta 24), reused 0 (delta 0)
Unpacking 25 objects
error: file write error (No space left on device)
fatal: unable to write sha1 file
unpack unpacker exited with error code
ng refs/heads/fdt n/a (unpacker error)
next reply other threads:[~2007-08-17 2:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-17 2:21 Jerry Van Baren [this message]
[not found] <46C4FADF.2020901@cideas.com>
2007-08-17 7:15 ` [U-Boot-Users] Oh-oh out of disk space on the server Wolfgang Denk
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=46C5061C.5040208@gmail.com \
--to=vanbargw@gmail.com \
--cc=u-boot@lists.denx.de \
/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