[gPXE-devel] [PULL] ipxe-sync

Marty Connor mdc at etherboot.org
Thu Jul 8 10:45:50 EDT 2010


Michael Brown wrote on 7/8/10 4:56 AM:
> On Thursday 08 Jul 2010 00:09:17 Marty Connor wrote:
>> Quoting numbers like 60% is poor form.
>
> You are welcome to keep it at 0%.  I have no particular interest in having my
> code backported into the gPXE tree.

But you seem just fine with using the 40% (by your calculations) of work 
from gPXE contributors that you have added to your iPXE fork. ;)

I also like the use of the word "backported", cleverly suggesting that 
iPXE is a successor to gPXE, rather than a recent derivative work with a 
suspiciously low bus factor. :)

> (It's nowhere near a perfect system of measurement, particularly if the
> committer forgets to add the relevant credits, but it does give a very good
> first approximation, and aims to ensure that the equally-worthwhile non-
> authorship contributions such as yours are not forgotten.)

Clever misdirection, but my point central remains.  Your numbers only 
count contributions _you_ have decided are "equally-worthwhile", which 
(surprise!) lets you once more promote your fork, iPXE!!  Wow, what an 
amazing coincidence! :)

> The EISA vendor ID in the handle used for PMM allocations (see
> PMM_HANDLE_BASE).  See the PMM spec for the relevant rules.

Thanks, we'll take a look and see if there are any potential issues here 
that need addressing.

>> I am also aware that there are a number of magic numbers in gPXE that
>> were embedded to help detect cases where people are using gPXE without
>> adhering to requirements the GPL, some of which are registered to your
>> company, Fen Systems.
>
> Yes, there are.  All of these are embedded within code over which I hold the
> copyright and so am the only person with legal standing to address any
> potential GPL violations.  If you encounter a suspected GPL violation, feel
> free to let me know and I can take appropriate action.
> Michael

Or, we can see about finding and removing the relevant code or rewriting 
it, and no longer have to deal with what you think is "appropriate".

My point being that there are multiple ways to deal with such 
situations, not just the one you propose.

/ Marty /



More information about the gPXE-devel mailing list