search for: revamp

Hi Folks, We've now reconnected the newgroup comp.emulators.ms-windows.wine to the wine-users mailing list, so they are, in theory, one 'virtual' community. We also revamped the web site a bit to try to make these things pop out a bit more. Please see this page in particular: http://www.winehq.org/site/getting_help Hopefully this will help people find a way to search for help and connect to the wine-users community a bit more easily, and ease some of the current...

On Thursday 11 of January 2018, Aki Tuomi wrote: > Seems we might've made a unexpected change here when we revamped the ssl > code. Revamped, interesting, can it support milions certs now on single machine? (so are certs loaded by demand and not wasting memory) > Aki -- Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org )

On Mon, Jul 25, 2016 at 05:47:05PM +0200, Pino Toscano wrote: > + if (path == NULL) > + path = "/usr/share/osinfo"; I wonder if we should use $prefix here. I guess there are arguments both ways. Should we just run the external osinfo-query program? Anyway it's fine as it stands, so ACK. Rich. -- Richard Jones, Virtualization Group, Red Hat

Newer versions do not have the 24px distributor.png icon; OTOH they have the 48px version, so look for that one before the 24px one. Also, bump the size limit to 10K, as newer versions of the icon are bigger than 3K. --- lib/inspect-icon.c | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/lib/inspect-icon.c b/lib/inspect-icon.c index 0cc8e92ad..623591aa6 100644 ---

It turns out that a) the standalone pep8 executable is deprecated in favour of pycodestyle b) $python-pep8 does not exist in modern distros and thus the style checks for Python scripts have been skipped for a long time. Instead, switch to pycodestyle directly, updating the list of ignored issues to the two categories left. --- config.sh.in | 1 + m4/guestfs-progs.m4 |

Hi Rafael, > 2) add a "byref" mark in the pointer argument. I think you mean "bycopy" or "byval" here. > 3) Have llvm-gcc create a copy before calling the function. Don't forget that the function may be called by code that was not compiled by LLVM. That's why we have to pay attention to the ABI! Solution (3) supposes we have control over both

Dear colleagues, I'm planning to debug usb connection with my new SONY CLIE handheld, and found that this process is much complicated by the fact usb.ko module can not be unloaded 'cause some process is referencing it: marck@revamp:~/tmp> kldstat -v -i 11 Id Refs Address Size Name 11 1 0xc0cf7000 1b000 usb.ko Contains modules: Id Name 62 usb/uhub 63 uhub/uhub 64 ohci/usb 65 uhci/usb 66 pci/uhci...

The existing implementation admitted that it was not very robust in the face of garbage input (including, but not limited to, the the fact that the scanf() family has undefined behavior on integer overflow). Tighten things up by reimplementing the function. The old comment mentioned the 'human*' interface from gnulib; we can't use that for licensing reasons; so my rewrite is done

> > 2) add a "byref" mark in the pointer argument. > > I think you mean "bycopy" or "byval" here. Yes, good catch. > > 3) Have llvm-gcc create a copy before calling the function. > > Don't forget that the function may be called by code that > was not compiled by LLVM. That's why we have to pay attention > to the ABI! Solution

This is my current understanding of the current situation and the proposed solution. Currently llvm-gcc compiles ----------------------- struct cpp_num { unsigned long high; unsigned long low; char unsignedp; }; void g(unsigned long); void f(struct cpp_num num) { g(num.high + 1); } ---------------------- into ---------------------------------------------------------------------------

...re recent versions of libosinfo switched the internal directory with the XML files of OSes to a different layout (still with the same XML format), causing libguestfs to not read them anymore. Furthermore, the internal directory is going to disappear soon, replaced by a public osinfo database [1]. Revamp the way libguestfs reads the data: first try the upcoming osinfo layout, falling back to the current libosinfo layout (which is the same as osinfo), and then to the old flat layout. [1] https://gitlab.com/libosinfo/libosinfo/blob/master/docs/database-layout.txt --- src/osinfo.c | 168 ++++++++++++...

Since I've heard about AsciiDoc (thanks ESR), I'm in the process of revamping the full Network UPS Tools documentation and website. Without going into the usual "it curred my desease, got my wife back home, and made me won a billion", it really saved my life ^_ ^ I was searching for such tool for years! thanks a lot Stuart and others. Kudos for the work! NUT...

Hi, attached a total revamp of the ssh-host-config and ssh-user-config scripts. The underlying idea is that one of our maintainers has contributed a unified configuration script environment for Cygwin, called csih. This is now used by the below ssh config scripts as well. There's also an additional file called sshd-inet...

The existing implementation admitted that it was not very robust in the face of garbage input; tighten things up by reimplementing the function, and add testsuite coverage to ensure further tweaks do not break things. The testsuite additions were interesting - we didn't have any easy way to link against a subset of the src/ files (all previous uses of the util functions have been through

I''m about to dive into a revamp of the payment processing engine for a my company''s software application service. I came across a tool called Service Merchant (http://servicemerchant.org), and it looks like it could be a good fit for me, especially since we do recurring monthly subscription billing. Has anyone tried usi...

On Thu, 11 Jan 2018 12:20:45 +0200, Aki Tuomi wrote: > Was the certificate path bundled in the server certificate? No, as a separate file, provided from the local (intermediate) CA: ssl_cert = </etc/openssl/certs/server.cert ssl_key = </etc/openssl/private/server.key ssl_ca = </etc/openssl/certs/ca-cert-chain.pem Worked fine with 2.2.x, 2.3 gives % openssl s_client -connect XXX:993

Hi Guys, I just realize that on the API documentation the code snippet is overflowing off the screen. Is this an intended behavior? Or who should I contact to get this one fixed. You can see the screenshot here: http://skitch.com/sikachu/dw82n/screen-shot-2553-08-30-at-16.24.26 Thanks :) Prem Sichanugrist -- You received this message because you are subscribed to the Google Groups "Ruby

...nd code review, the brand new ConfBridge application has been officially merged into Asterisk Trunk!!! http://svnview.digium.com/svn/asterisk?view=revision&revision=314598 If you are already familiar with ConfBridge from Asterisk 1.6.X and 1.8, forget everything you know. This is a completely revamped, highly optimized, and feature rich conferencing application capable of mixing sample rates from 8khz all the way up to 192khz! Exciting right?! So Go! use it, test it, and report back! Tell us what you like, what you don't like, if you want a feature that doesn't yet exist, and report...

...0 0 0 0 0 0 0 0 0 0 [6,] 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 But I am thinking that there has to be a better way particularly because I'll get an error if I set lagnum to 3. Any improvements or total revampings are appreciated. The number of columns will always be a multiple of the number of rows So K doesn't have to be 6. that was just to show what the commands do. thanks. -------------------------------------------------------- This is not an offer (or solicitation of an offer) to buy/se...{{dr...

...affect on pre-existing code since we already call readULEB128(...) for the call-site table length. High bit set for 3 bytes results in 4 byte read as per uleb128. This is obvious now that I've taken time to write this, but hey if nothing else it helps the list. :-) Garrison PS: Are you still revamping the llvm exception API as you proposed a couple of months ago, or was this effort ditched? On Feb 5, 2010, at 20:44, Bill Wendling wrote: > On Feb 5, 2010, at 4:00 PM, Duncan Sands wrote: > >> Hi Bill, >> >>> It looks like your goal is to keep the 32-bit pointers...