[gPXE-devel] Fwd: Re: [Xen-devel] tools: gpxe link error

[Keir Fraser]

On 19/07/2010 17:09, "Keir Fraser" <keir.fraser at eu.citrix.com> wrote:

>> ROMs need to have explicit PCI vendor and device IDs, which are put in
>> the ROM header so the BIOS can load them for appropriate PCI devices.
>> 
>> Hope this helps.  We need to fix this in gpxe.git.
> 
> Christoph: Please test this and, if it works for you, submit it as a patch
> against our gpxe tarball, as you did for your previous patch.

Oh, hang on a minute. It may just be that our gpxe snapshot is real old.
Certainly our tarball is way older than the commit you mention, so the issue
is not that, and indeed it may no longer exist in your repo. I think
Christoph should try the tip of your repository. Sorry, I should have
suggested that first!

This makes the below more pressing then. How should we sync with you?

 -- Keir

>> Keir: Are you tracking gpxe.git/master for Xen?  Thanks for letting
>> gpxe-devel know about this issue.
> 
> No we have a tarball snapshot of the git repository, originally taken in
> September 2008 and never updated since. The issue here is that afaik you
> don't do releases out of your repository, so it's not like we could pull
> your repo and check out a tagged release. I could clone your repo in our
> build system, and check out a known changeset which I update across stable
> releases of Xen, I suppose. The original thinking is that I want our builds
> to be reasonably deterministic, and taking a snapshot tarball is easy.
> 
> Is there any structure in your git repo in terms of stable versus
> development branches? That is, are we guaranteed to get a pretty good set of
> bits generated from any pull of the main branch of your public repository?