| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
RE: [Xen-devel] default xen "make world" again dependent on non-xenbits
> 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.
Thanks,
Dan
> -----Original Message-----
> From: Ian Jackson [mailto:Ian.Jackson@xxxxxxxxxxxxx]
> Sent: Wednesday, October 07, 2009 9:24 AM
> To: Dan Magenheimer
> Cc: Xen-Devel (E-mail)
> Subject: Re: [Xen-devel] default xen "make world" again dependent on
> non-xenbits repositories and non-http protocol
>
>
> Dan Magenheimer writes ("[Xen-devel] default xen "make world"
> again dependent on non-xenbits repositories and non-http protocol"):
> > Argh! I know there's been a lot of effort over the years
> > on driving the Xen build mechanism to work from a single
> > server (xenbits). I notice that (probably for awhile, but
> > I just noticed it) a default "make world" on a fresh
> > clone again depends on a different server, namely
> > git.kernel.org.
>
> 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.
>
> The kernel is big and has complex development processes and running
> our own infrastructure for hosting it doesn't seem sensible.
>
> And, of course, building it is optional (although enabled by default).
>
> Ian.
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
>
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home