Displaying 5 results from an estimated 5 matches for "48e94f4fa7b3c3".
2017 Mar 26
3
where to swap
...as "can be ignored" in the the text which i
> quoted before my statement.
>
Translation to a more plain language (so to avoid calling both, the
original code and the patch too, as "code", or both being "it"):
You are suggesting to revert the (wrong) commit 48e94f4fa7b3c3..., and
then the whole complete "correct" patch that Martin posted should be
applied, not just the first part, but the second part too.
>From my prior post, two items remain to be seen:
_ clarification from Martin (since I asked a similar question regarding
his own email/wording);...
2017 Mar 26
3
where to swap
...orrupt CX.
> And given that space in isohdpfx is very limited (432 bytes) perhaps
> the right thing might be to not have that xor in there.
>
> But then better safe than sorry, and given that there is space _now_,
> why not?
>
>
> > _ after reverting the (wrong) commit 48e94f4fa7b3c3..., whether the 2
> > sections of Martin's patch should rather be applied as one commit, or 2
> > separate commits, or just the first part of the patch should be
> > applied.
>
> The patch in <http://www.syslinux.org/archives/2017-March/025706.html>
> should...
2017 Mar 26
2
where to swap
Thomas wrote:
> I think it still has good reason to exist.
Would you please clarify what do you mean with "it"? What exactly
should exist? By "it", do you mean the original code, or the patch? Do
you mean that the original code (in this section of the file) should
remain as it was/is, without applying the relevant part of Martin's
patch? Or instead, do you mean
2017 Mar 26
0
where to swap
...now that David's BIOS _didn't_ corrupt CX.
And given that space in isohdpfx is very limited (432 bytes) perhaps
the right thing might be to not have that xor in there.
But then better safe than sorry, and given that there is space _now_,
why not?
> _ after reverting the (wrong) commit 48e94f4fa7b3c3..., whether the 2
> sections of Martin's patch should rather be applied as one commit, or 2
> separate commits, or just the first part of the patch should be
> applied.
The patch in <http://www.syslinux.org/archives/2017-March/025706.html>
should be applied after reverting
48...
2017 Mar 26
0
where to swap
...that space in isohdpfx is very limited (432 bytes) perhaps
>> the right thing might be to not have that xor in there.
>>
>> But then better safe than sorry, and given that there is space _now_,
>> why not?
>>
>>
>> > _ after reverting the (wrong) commit 48e94f4fa7b3c3..., whether the 2
>> > sections of Martin's patch should rather be applied as one commit, or 2
>> > separate commits, or just the first part of the patch should be
>> > applied.
>>
>> The patch in <http://www.syslinux.org/archives/2017-March/025706.html...