From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Nathan March <nathan@gt.net>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
xen-devel mailing list <xen-devel@lists.xensource.com>
Subject: Re: Updated git locations now that kernel.org is no longer hosting?
Date: Wed, 7 Sep 2011 17:03:34 -0400 [thread overview]
Message-ID: <20110907210334.GA20800@dumpdata.com> (raw)
In-Reply-To: <4E67D0A9.4030101@gt.net>
On Wed, Sep 07, 2011 at 01:14:33PM -0700, Nathan March wrote:
>
> On 9/7/2011 1:10 PM, Jeremy Fitzhardinge wrote:
> >On 09/07/2011 12:36 PM, Nathan March wrote:
> >>Hi,
> >>
> >>Just wondering if anyone can point me to the new locations for
> >>xen/next-3.0 repo?
> >That's a branch name. Which specific repo are you looking for?
> >
> >I'm using github (git://github.com/jsgf/linux-xen.git), but I don't
> >recommend any the branches there for use as-is.
> >
> > J
>
> Oops, was looking for either jeremy or konrad's trunk.
>
> Running into an issue with vm's not-responding under high IO load
> and am looking to try tapdisk2 again, switched to blkback when going
> to mainline linux 3.0. Looking for whatever would be considered the
> stable 3.x with tapdisk2 support?
http://xenbits.xen.org/gitweb/?p=people/dstodden/blktap-debian.git;a=summary
or perhaps
http://xenbits.xen.org/gitweb/?p=people/dstodden/linux.git;a=summary
or
http://xenbits.xen.org/gitweb/?p=people/dstodden/blktap.git;a=summary
?
>
> - Nathan
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
prev parent reply other threads:[~2011-09-07 21:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-07 19:36 Updated git locations now that kernel.org is no longer hosting? Nathan March
2011-09-07 20:10 ` Jeremy Fitzhardinge
2011-09-07 20:14 ` Nathan March
2011-09-07 21:03 ` Konrad Rzeszutek Wilk [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=20110907210334.GA20800@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=jeremy@goop.org \
--cc=nathan@gt.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.