From: Stefan Kuhne <stefan.kuhne@gmx.net>
To: xen-devel@lists.xensource.com
Subject: Re: Jeremys GIT repo hangs
Date: Sat, 19 Jun 2010 20:45:27 +0200 [thread overview]
Message-ID: <4C1D1047.8030203@access.denied> (raw)
In-Reply-To: <20100619121439.GC17817@reaktio.net>
[-- Attachment #1.1: Type: text/plain, Size: 334 bytes --]
Am 19.06.2010 14:14, schrieb Pasi Kärkkäinen:
> On Sat, Jun 19, 2010 at 02:10:02PM +0200, Stefan Kuhne wrote:
Hello Pasi,
> This is usually caused by a firewall problem/bug/misconfiguration.
>
git was running out of ram.
My DomU had 128MB with 256MB does it work.
Should i tell this to git?
Regards,
Stefan Kuhne
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 552 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
prev parent reply other threads:[~2010-06-19 18:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-19 12:10 Jeremys GIT repo hangs Stefan Kuhne
2010-06-19 12:14 ` Pasi Kärkkäinen
2010-06-19 13:00 ` Stefan Kuhne
2010-06-19 13:08 ` Pasi Kärkkäinen
2010-06-19 18:45 ` Stefan Kuhne [this message]
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=4C1D1047.8030203@access.denied \
--to=stefan.kuhne@gmx.net \
--cc=xen-devel@lists.xensource.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).