From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
"Xen-Devel (E-mail)" <xen-devel@lists.xensource.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: RE: default xen "make world" again dependent on non-xenbits repositories and non-http protocol
Date: Wed, 7 Oct 2009 09:26:13 -0700 (PDT) [thread overview]
Message-ID: <cdd20d93-0a0f-4bc3-a601-dca7a65f16e9@default> (raw)
In-Reply-To: <alpine.DEB.2.00.0910071709200.25583@kaball-desktop>
> We could make everyone happy using git over http:
Excellent. +1!
> +XEN_LINUX_GIT_URL ?=
> http://www.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> :
> but the problem is that it seems to be broken for Jeremy's tree (the
> others work fine).
I'm told that Jeremy needs to set something in his git config
file on kernel.org for this to work.
> -----Original Message-----
> From: Stefano Stabellini [mailto:stefano.stabellini@eu.citrix.com]
> Sent: Wednesday, October 07, 2009 10:12 AM
> To: Dan Magenheimer
> Cc: Ian Jackson; Xen-Devel (E-mail)
> Subject: RE: [Xen-devel] default xen "make world" again dependent on
> non-xenbits repositories and non-http protocol
>
>
> On Wed, 7 Oct 2009, Dan Magenheimer wrote:
> > > As far as I'm concerned we've made a conscious decision to make an
> > > exception for git.kernel.org, which is after all a very
> high-profile
> > > site that a lot of people depend on which ought not to be
> down very
> > > often or for very long.
> >
> > Understood, but the problem (in this case) is not the server
> > but the protocol... I don't claim to understand this well, but
> > I'm told that git isn't handled by standard proxies.
> >
> > I believe there's an http hg mirror for the kernel but
> > I don't know if it works for anything but the main branch.
> >
> > Lacking any other solution, is there any easy way for "make world"
> > to determine immediately if git.kernel.org is NOT accessible
> > via the git protocol (or at least via something like "make check")?
> >
> > OR as an absolute minimum the issue should be in the main README.
> >
> > Yes, I know I should be able to work around this, but I am
> > in part speaking up for all the newbies that would like to work
> > on Xen but find "getting started" is too difficult.
> >
>
> We could make everyone happy using git over http:
>
> diff -r 6f63970032a3 buildconfigs/mk.linux-2.6-pvops
> --- a/buildconfigs/mk.linux-2.6-pvops Fri Oct 02 09:10:27 2009 +0100
> +++ b/buildconfigs/mk.linux-2.6-pvops Wed Oct 07 17:11:07 2009 +0100
> @@ -5,7 +5,7 @@
>
> XEN_LINUX_CONFIG_UPDATE := buildconfigs/enable-xen-config
>
> -XEN_LINUX_GIT_URL ?=
> git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> +XEN_LINUX_GIT_URL ?=
> http://www.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> XEN_LINUX_GIT_REMOTEBRANCH ?= xen/master
>
> EXTRAVERSION ?=
> diff -r 6f63970032a3 buildconfigs/mk.linux-2.6-tip-latest
> --- a/buildconfigs/mk.linux-2.6-tip-latest Fri Oct 02
> 09:10:27 2009 +0100
> +++ b/buildconfigs/mk.linux-2.6-tip-latest Wed Oct 07
> 17:11:07 2009 +0100
> @@ -5,7 +5,7 @@
>
> XEN_LINUX_CONFIG_UPDATE := buildconfigs/enable-xen-config
>
> -XEN_LINUX_GIT_URL ?=
> git://git.kernel.org/pub/scm/linux/kernel/git/x86/linux-2.6-tip.git
> +XEN_LINUX_GIT_URL ?=
> http://www.kernel.org/pub/scm/linux/kernel/git/x86/linux-2.6-tip.git
> XEN_LINUX_GIT_REMOTEBRANCH ?= auto-latest
>
> EXTRAVERSION ?=
>
> ---
>
> but the problem is that it seems to be broken for Jeremy's tree (the
> others work fine).
>
>
next prev parent reply other threads:[~2009-10-07 16:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-28 22:17 default xen "make world" again dependent on non-xenbits repositories and non-http protocol Dan Magenheimer
2009-10-07 15:23 ` Ian Jackson
2009-10-07 15:42 ` Dan Magenheimer
2009-10-07 16:11 ` Stefano Stabellini
2009-10-07 16:26 ` Dan Magenheimer [this message]
2009-10-07 16:30 ` Keir Fraser
2009-10-07 23:49 ` Jeremy Fitzhardinge
2009-10-07 16:26 ` Konrad Rzeszutek Wilk
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=cdd20d93-0a0f-4bc3-a601-dca7a65f16e9@default \
--to=dan.magenheimer@oracle.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=jeremy@goop.org \
--cc=stefano.stabellini@eu.citrix.com \
--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.