search for: sepearete

Displaying 6 results from an estimated 6 matches for "sepearete".

Did you mean: separete
2014 Jan 02
2
[syslinux:firmware] version: Bump version & Lua
"H. Peter Anvin" <hpa at zytor.com> writes: > On 12/12/2013 12:31 AM, Ferenc Wagner wrote: > >> Shall I rebase it to the current firmware head? >> >> Also, 5.2.3 was released a couple of days ago. It's a bugfix release. >> I made it into a sepearete commit (pushed). >> >> Better default Lua paths (source and binary) would be useful. Shall I >> mirror the Syslinux PATH at initialization [...] ? > > All of this sounds like a good idea. I implemented them, but the EFI build problems keep getting in the way... Shall I p...
2013 Dec 12
3
[syslinux:firmware] version: Bump version & Lua
...>> I have done a `git pull`, but can't see the new Lua version. >> >> Is Lua 5.2.2 in 6.03? > > No, it still needs to be merged. Shall I rebase it to the current firmware head? Also, 5.2.3 was released a couple of days ago. It's a bugfix release. I made it into a sepearete commit (pushed). Better default Lua paths (source and binary) would be useful. Shall I mirror the Syslinux PATH at initialization, or use some static value? Also, header dependencies are not tracked, as no .*.d are generated under the com32/lua directory. Should they be enabled manually, or sho...
2013 Dec 11
2
[syslinux:firmware] version: Bump version & Lua
Op 2013-12-11 om 02:09 schreef syslinux-bot for Matt Fleming: > Commit-ID: 5e59ac11d6d105591d6da742750ea2f804534d43 > Gitweb: http://www.syslinux.org/commit/5e59ac11d6d105591d6da742750ea2f804534d43 > Author: Matt Fleming <matt.fleming at intel.com> > AuthorDate: Wed, 11 Dec 2013 10:03:13 +0000 > Committer: Matt Fleming <matt.fleming at intel.com> >
2013 Dec 13
0
[syslinux:firmware] version: Bump version & Lua
On 12/12/2013 12:31 AM, Ferenc Wagner wrote: > > Shall I rebase it to the current firmware head? > > Also, 5.2.3 was released a couple of days ago. It's a bugfix release. > I made it into a sepearete commit (pushed). > > Better default Lua paths (source and binary) would be useful. Shall I > mirror the Syslinux PATH at initialization, or use some static value? > > Also, header dependencies are not tracked, as no .*.d are generated > under the com32/lua directory. Should th...
2014 Jan 02
0
version: Bump version & Lua
...t;hpa at zytor.com> writes: > > > On 12/12/2013 12:31 AM, Ferenc Wagner wrote: > > > >> Shall I rebase it to the current firmware head? > >> > >> Also, 5.2.3 was released a couple of days ago. It's a bugfix release. > >> I made it into a sepearete commit (pushed). > >> > >> Better default Lua paths (source and binary) would be useful. Shall I > >> mirror the Syslinux PATH at initialization [...] ? > > > > All of this sounds like a good idea. > > I implemented them, but the EFI build problems ke...
2014 Jan 02
1
version: Bump version & Lua
...writes: >> >>> On 12/12/2013 12:31 AM, Ferenc Wagner wrote: >>> >>>> Shall I rebase it to the current firmware head? >>>> >>>> Also, 5.2.3 was released a couple of days ago. It's a bugfix release. >>>> I made it into a sepearete commit (pushed). >>>> >>>> Better default Lua paths (source and binary) would be useful. Shall I >>>> mirror the Syslinux PATH at initialization [...] ? >>> >>> All of this sounds like a good idea. >> >> I implemented them, but th...