search for: nogit

...elcome. Debian already does what it needs: http://sources.debian.net/src/syslinux/3:6.03%2Bdfsg-4/debian/patches/00 04-gnu-efi-git.patch/ As an additional example, Mageia solves it for its development environment: http://svnweb.mageia.org/packages/cauldron/syslinux/current/SOURCES/sysl inux-nogit.patch?view=markup&pathrev=600959 If you are using Ubuntu 14.04 and you want to use Syslinux 6.03, then either: _ use the Debian relevant packages related to Syslinux 6.03; or, _ use the built-in binaries already included in the official upstream distribution archives from kernel.org. Offi...

On mageia I'm using the following patch https://svnweb.mageia.org/packages/cauldron/syslinux/current/SOURCES/syslinux-nogit.patch?revision=600959&view=markup If it does solve your issue to, I could try pushing it into the repo. 2015-09-16 8:44 GMT+02:00 Thomas Letan via Syslinux <syslinux at zytor.com>: > Hi. > > Sometimes, it may happen that we do not want to clone a repo (here the > submodule...

I really think we should not take chances; Syslinux source should include (probably as an optional download tarball) the gnu-efi used to build the particular Syslinux version. Pat -------------------------------------------- On Mon, 12/22/14, Ady <ady-sf at hotmail.com> wrote: Subject: Re: [syslinux] check-gnu-efi.sh: print the output of build-gnu-efi.sh To: syslinux at zytor.com

...we are supposed to use tarballs. To avoid this issue, I've been adding a very stupid fix to my build. What's you opinion on it ? At least, with it, I can build syslinux from the tarball. Erwan, -------------- next part -------------- A non-text attachment was scrubbed... Name: syslinux-nogit.patch Type: text/x-patch Size: 258 bytes Desc: not available URL: <http://www.zytor.com/pipermail/syslinux/attachments/20140307/5efbda99/attachment.bin>

Hi, In efi/build-gnu-efi.sh, there's a "git submodule update --init" command which is causing a compilation issue on my build. I currently build in an offline environment so doing a git update isn't possible. Should this command be included only for development? Thanks, Mike

On Wed, Sep 16, 2015 at 10:55 AM, Erwan Velu via Syslinux <syslinux at zytor.com> wrote: > On mageia I'm using the following patch > https://svnweb.mageia.org/packages/cauldron/syslinux/current/SOURCES/syslinux-nogit.patch?revision=600959&view=markup > > > If it does solve your issue to, I could try pushing it into the repo. Commit ID 0f8cbe04 was 8 months ago. Thank you for your contribution. -- -Gene > 2015-09-16 8:44 GMT+02:00 Thomas Letan via Syslinux <syslinux at zytor.com>: >...

...2:00 Gene Cumm <gene.cumm at gmail.com>: > On Wed, Sep 16, 2015 at 10:55 AM, Erwan Velu via Syslinux > <syslinux at zytor.com> wrote: > > On mageia I'm using the following patch > > > https://svnweb.mageia.org/packages/cauldron/syslinux/current/SOURCES/syslinux-nogit.patch?revision=600959&view=markup > > > > > > If it does solve your issue to, I could try pushing it into the repo. > > Commit ID 0f8cbe04 was 8 months ago. Thank you for your contribution. > > -- > -Gene > > > 2015-09-16 8:44 GMT+02:00 Thomas Letan vi...

With the numbers of patches flying around it can be a bit hard for a maintainer to spot patches which (s)he is expected to comment on / deal with, especially now that we have a larger number of maintainers of varying subsystems etc. I think it might be time to start asking patch submitters to CC the maintainers of the code they are touching, based on the MAINTAINERS file. If people (specifically

2015-09-15 13:57 UTC+02:00, Patrick Masotta <masottaus at yahoo.com>: >>>> > > What's the default strategy for checking out new gnu-efi sources? > > We should have a way to set the version we want to work with > > and only update when we want to do so. > > That's true. All I did in these patches was to inline those shell > scripts in the

I think I might be mad to include that many mailing lists in this patchset... As I explained in [PATCH 1/5], fstests covers more and more fs testing thing, so we always get help from fs specific mailing list, due to they learn about their features and bugs more. Besides that, some folks help to review patches (relevant with them) more often. So I'd like to bring in the similar way of

We are in the process of an Asterisk call center deployment using IAX2 G711 ulaw softphones. Outbound sound quality is terrible. This week we rebuilt the entire LAN with Cisco 2950-EI switches and have employed QoS on the switches and router. Still sounds terrible. What we are now finding is that the network card in the PC may be the key to the problem. A Dell Optiplex P4 2.4GHz 512MB

...n`; my @new_patterns = split('\n', $pattern_files); $pattern_files = join(' ', @new_patterns); next if ($pattern_files =~ /^\s*$/); # Find the section the first file matches my $pattern_file = @new_patterns[0]; my $section_output = `./scripts/get_maintainer.pl --nogit --nogit-fallback --sections --pattern-depth=1 $pattern_file`; my @section = split('\n', $section_output); my $section_header = @section[0]; print("Section: <$section_header>\n"); # Skip the section if it's already done print("Already done '$sec...

...n`; my @new_patterns = split('\n', $pattern_files); $pattern_files = join(' ', @new_patterns); next if ($pattern_files =~ /^\s*$/); # Find the section the first file matches my $pattern_file = @new_patterns[0]; my $section_output = `./scripts/get_maintainer.pl --nogit --nogit-fallback --sections --pattern-depth=1 $pattern_file`; my @section = split('\n', $section_output); my $section_header = @section[0]; print("Section: <$section_header>\n"); # Skip the section if it's already done print("Already done '$sec...

...n`; my @new_patterns = split('\n', $pattern_files); $pattern_files = join(' ', @new_patterns); next if ($pattern_files =~ /^\s*$/); # Find the section the first file matches my $pattern_file = @new_patterns[0]; my $section_output = `./scripts/get_maintainer.pl --nogit --nogit-fallback --sections --pattern-depth=1 $pattern_file`; my @section = split('\n', $section_output); my $section_header = @section[0]; print("Section: <$section_header>\n"); # Skip the section if it's already done print("Already done '$sec...

...n`; my @new_patterns = split('\n', $pattern_files); $pattern_files = join(' ', @new_patterns); next if ($pattern_files =~ /^\s*$/); # Find the section the first file matches my $pattern_file = @new_patterns[0]; my $section_output = `./scripts/get_maintainer.pl --nogit --nogit-fallback --sections --pattern-depth=1 $pattern_file`; my @section = split('\n', $section_output); my $section_header = @section[0]; print("Section: <$section_header>\n"); # Skip the section if it's already done print("Already done '$sec...

...n`; my @new_patterns = split('\n', $pattern_files); $pattern_files = join(' ', @new_patterns); next if ($pattern_files =~ /^\s*$/); # Find the section the first file matches my $pattern_file = @new_patterns[0]; my $section_output = `./scripts/get_maintainer.pl --nogit --nogit-fallback --sections --pattern-depth=1 $pattern_file`; my @section = split('\n', $section_output); my $section_header = @section[0]; print("Section: <$section_header>\n"); # Skip the section if it's already done print("Already done '$sec...