xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Stephan Seitz <stse+xen@fsing.rootsland.net>
To: xen-devel@lists.xensource.com
Subject: Re: Jeremy's GIT-tree and network problems
Date: Mon, 3 May 2010 20:48:41 +0200	[thread overview]
Message-ID: <20100503T2046.GA.edd2d.stse@fsing.rootsland.net> (raw)
In-Reply-To: <4BB0F4A0.2000403@goop.org>


[-- Attachment #1.1: Type: text/plain, Size: 651 bytes --]

On Mon, Mar 29, 2010 at 11:42:40AM -0700, Jeremy Fitzhardinge wrote:
>Fortunately it looks like this is going to get some systematic 
>attention. I'd really like any reasonable (ie, not inherently broken for 
>other reasons) network setup to just work.

Do you know what is the status of this problem

At the moment I’m using 2.6.33.2 with xen-patches-2.6.33-1.tar.bz2 and 
everything is working fine. So if you think, the bug is fixed in your 
tree, I’ll try it.

Shade and sweet water!

	Stephan

-- 
| Stephan Seitz             E-Mail: stse@fsing.rootsland.net |
| PGP Public Keys: http://fsing.rootsland.net/~stse/pgp.html |

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

      parent reply	other threads:[~2010-05-03 18:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-29 15:40 Jeremy's GIT-tree and network problems Stephan Seitz
2010-03-29 18:18 ` S.H. Verbrugge
2010-03-30 12:26   ` Stephan Seitz
2010-03-30 14:30     ` Konrad Rzeszutek Wilk
2010-03-30 19:39       ` Stephan Seitz
2010-03-29 18:42 ` Jeremy Fitzhardinge
2010-03-30 12:33   ` Stephan Seitz
2010-05-03 18:48   ` Stephan Seitz [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=20100503T2046.GA.edd2d.stse@fsing.rootsland.net \
    --to=stse+xen@fsing.rootsland.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).