search for: undisput

I spoke with Markus before Christmas (I hope all your holidays were better then mine.. But that's another topic. Car are evil.=) and he would like to release 2.4.0 in the very near future. Is there any undisputed patches still out not applied to the current portable CVS tree? (BTW, I just applied the getrlimit patch from Corinna.) - Ben

...turn it off if it didn't lock up all by itself.... It is so very sad that some providers don't monitor their own people. I see where comcast has now slid down to number 8 after holding the number one spot as the biggest spammer network for a very long time. Good for them! It seems the undisputed king of this world now is verizonbusiness.com.... bad bad very bad.... Sorry.. yeah.. a bit off topic...... John Hinton

On Thu, Nov 15, 2018 at 11:38:35PM +0100, Linus Walleij wrote: > On Thu, Nov 15, 2018 at 11:17 PM Fernando Ramos <greenfoo at gluegarage.com> wrote: > > > One of the things in the DRM TODO list ("Documentation/gpu/todo.rst") was to > > "switch from reference/unreference to get/put". That's what this patch series is > > about. > > The

On Thu, Nov 15, 2018 at 11:38:35PM +0100, Linus Walleij wrote: > On Thu, Nov 15, 2018 at 11:17 PM Fernando Ramos <greenfoo at gluegarage.com> wrote: > > > One of the things in the DRM TODO list ("Documentation/gpu/todo.rst") was to > > "switch from reference/unreference to get/put". That's what this patch series is > > about. > > The

Hi, Ady wrote: > If users want to find the "--uefi" parameter for the isohybrid command, > it is already there, documented. Yes. But it does only work with non-SYSLINUX boot images. It is undisputed that one can work around that problem on a hard-disk-like medium by simply not using ISO 9660 but a set of partitions and SYSLINUX EFI software. But this does not help with optical media. There the El Torito specs clearly define the boot catalog and images as parasites of an ISO 9660 filesystem....

...ctory are trademarks of Microsoft Corporation. About the Samba Team ==================== The Samba Team is a worldwide group of computer professionals working together via the Internet to produce the highest quality Free Software Windows (SMB3/SMB2/SMB/CIFS) server and client software. We are the undisputed experts in providing interoperability with computers running Microsoft Windows. Members of the Samba Team work for many of the largest companies in the software Industry and even helped Microsoft produce the protocol documentation that fully specifies the SMB/CIFS protocol.

...ctory are trademarks of Microsoft Corporation. About the Samba Team ==================== The Samba Team is a worldwide group of computer professionals working together via the Internet to produce the highest quality Free Software Windows (SMB3/SMB2/SMB/CIFS) server and client software. We are the undisputed experts in providing interoperability with computers running Microsoft Windows. Members of the Samba Team work for many of the largest companies in the software Industry and even helped Microsoft produce the protocol documentation that fully specifies the SMB/CIFS protocol.

...in the stream. The debate is not over wether this is a good way of doing it, but rather, wether treating different codecs/streams differently is a good idea. Before you argue this you had better read Monty's full documentation on this since it was published months ago. II. Undisputed API changes and extentions A. Namespace change One of the very good ideas to come from the Annodex crew was to provide libogg1 backwards compatability. Toward this goal all libogg2-specific functions and structures have been renamed so that, in the near future, functions and struc...

...in the stream. The debate is not over wether this is a good way of doing it, but rather, wether treating different codecs/streams differently is a good idea. Before you argue this you had better read Monty's full documentation on this since it was published months ago. II. Undisputed API changes and extentions A. Namespace change One of the very good ideas to come from the Annodex crew was to provide libogg1 backwards compatability. Toward this goal all libogg2-specific functions and structures have been renamed so that, in the near future, functions and struc...

...in the stream. The debate is not over wether this is a good way of doing it, but rather, wether treating different codecs/streams differently is a good idea. Before you argue this you had better read Monty's full documentation on this since it was published months ago. II. Undisputed API changes and extentions A. Namespace change One of the very good ideas to come from the Annodex crew was to provide libogg1 backwards compatability. Toward this goal all libogg2-specific functions and structures have been renamed so that, in the near future, functions and struc...

...in the stream. The debate is not over wether this is a good way of doing it, but rather, wether treating different codecs/streams differently is a good idea. Before you argue this you had better read Monty's full documentation on this since it was published months ago. II. Undisputed API changes and extentions A. Namespace change One of the very good ideas to come from the Annodex crew was to provide libogg1 backwards compatability. Toward this goal all libogg2-specific functions and structures have been renamed so that, in the near future, functions and struc...

...in the stream. The debate is not over wether this is a good way of doing it, but rather, wether treating different codecs/streams differently is a good idea. Before you argue this you had better read Monty's full documentation on this since it was published months ago. II. Undisputed API changes and extentions A. Namespace change One of the very good ideas to come from the Annodex crew was to provide libogg1 backwards compatability. Toward this goal all libogg2-specific functions and structures have been renamed so that, in the near future, functions and struc...

On 22/03/2016 16:35, Thomas Schmitt via Syslinux wrote: ... > How can we augment > http://www.syslinux.org/wiki/index.php?title=ISOLINUX > http://www.syslinux.org/wiki/index.php?title=Isohybrid > so that users do not believe to have missed the trick for UEFI booting > from optical media ? +1. I have read Ady's answer to this message, but still: why not just state clearly in

...*byte*code in 2.0/2.1. I need a definitive word on this to proceed. My understanding is that bytecode is already gone, but there are still some functions/enums that really deal with *byte*code (instead of *bit*code). I did not touch those areas, so the attached patch is for review about the IMO undisputed changes. What is still missing: - removing any genuine bytecode stuff (magic/filetype detection, etc.) - Configury/Makefiles related sanitizing - doc changes (.pod and .html files) - anything else grep comes up with (should be next to nothing) If anybody feels the urge to review the attached...

heyas- I believe there is a need for a standard vorbis comment field to encode "Total Number of Tracks (on a CD)". Why we need this -------------------- - Existing Vorbis programs already implement this, inconsistently, and hence don't interoperate. These seems the key reason to me. - MP3s include this - Some software (e.g., iTunes) uses this information, e.g., to display