search for: wavy

...ndwidth. We moved videos to Youtube to offload the bandwidth, and moving the code to GitHub shares the same mindset. > Possibly, I don’t know, but that’s exactly why I asked for first hand data on the subject (i.e. Anton and/or Tanya) about hosting the git/SVN repos themselves, instead of hand-wavy “I believe” discussions. Bear in mind that I gave you facts (bandwidth problems, turned off SVN services, constant breakdowns, expertise in handling traffic, backup solutions). I also made you aware that the human cost is not *just* Tanya and Anton, but also me and everyone else that maintains bu...

...significant > bandwidth consumer, otherwise no it does not make sense. > > > > > > >> Possibly, I don’t know, but that’s exactly why I asked for first hand > data on the subject (i.e. Anton and/or Tanya) about hosting the git/SVN > repos themselves, instead of hand-wavy “I believe” discussions. > > > > Bear in mind that I gave you facts (bandwidth problems, turned off SVN > > services, constant breakdowns, expertise in handling traffic, backup > > solutions). > > And I consider many of the “facts” you gave to conflate other element th...

...t;> > If we're still talking about applying it to the HEAD, not the whole >> > history, I think it's feasible. >> >> Yep, to be clear, I mean one big change to head, not trying to rewrite >> history. > > > I think rewriting history is kind of a hand-wavy pipe dream. ;] I'll > believe it when I see it. For now, we should stick to what we know we could > actually do, and changing head is the only realistic option there. > FWIW - I don't think we even have that power (when it comes to global renaming) yet, do we? (rename everything i...

...ogic simpler to start with, AND provide a base so that people can just write the majority of their driver logic in rust, which is where the language "safety" issues are most needed, not in the lifecycle rules involving the internal driver model infrastructure. Anyway, that's all hand-wavy right now, sorry, to get back to the point here, again, let's take this, which will allow the firmware bindings to be resubmitted and hopefully accepted, and we can move forward from there to "real" things like a USB or PCI or even platform device and driver binding stuff. thanks, g...

...h the points in order to obtain a smooth representation and then take derivatives of this. Also tried to smooth it, and used an SG differentiator. Results are rather poor so far, in the sense that you can see from the graph that the derivative function is a straight line but I am getting pretty wavy things back.) thanks for any advice, eugene.

Hello All, Recently, I build three Asterisk 1.4 box and installed licensed copy of G729 codec. Before installing the G729 codec I tested the MOH on all three Asterisks box and it was working fine. So I install G729 codec and retested MOH and it was all wavy... Meaning the music was going up and down and missing bits and pieces and choppy... Any idea what did I do wrong? The MOH files are the default ones which comes with Asterisk. Cheers, Neel

On Fri, Jun 07, 2024 at 02:36:50PM +0200, Greg KH wrote: > Anyway, that's all hand-wavy right now, sorry, to get back to the point > here, again, let's take this, which will allow the firmware bindings to > be resubmitted and hopefully accepted, and we can move forward from > there to "real" things like a USB or PCI or even platform device and > driver bindin...

...there because of the implicit/explicit template > instantiation stuff. there are several functions in the example you sent, some linkonce and some available_externally. Which ones shouldn't be there and why? Can you please give more details about why it is a problem - it was kind of hand-wavy so far :) Thanks, Duncan.

On Fri, Jun 07, 2024 at 03:33:39PM +0200, Danilo Krummrich wrote: > On Fri, Jun 07, 2024 at 02:36:50PM +0200, Greg KH wrote: > > Anyway, that's all hand-wavy right now, sorry, to get back to the point > > here, again, let's take this, which will allow the firmware bindings to > > be resubmitted and hopefully accepted, and we can move forward from > > there to "real" things like a USB or PCI or even platform device and &gt...

On 19 July 2016 at 22:35, Mehdi Amini <mehdi.amini at apple.com> wrote: > Claiming that it "will be *a lot* less” burden that now is easy, but I don’t see any obvious fact to back this up. > What is the current maintenance requirement of SVN/Git? Can someone who knows provides some fact? I'll let Anton tell his side, and Tanya talk about the real costs, but here are some

...h better tooling for tracking compile time in the future, we'll reach a state where we'll be able to consider "breaking" the compile-time regression test as important as breaking any test: i.e. the offending commit should be reverted unless it has been shown to significantly (hand wavy...) improve the runtime performance. Since you raise the discussion now, I take the opportunity to push on the "more aggressive" side: I think the policy should be a balance between the improvement the commit brings compared to the compile time slow down. Something along the line as what...

On Dec 4, 2009, at 12:52 AM, Duncan Sands wrote: > Hi Bill, > >> There's a problem with your check-in for r72619 is causing "weak >> external" symbols to appear in C++ code when it shouldn't. Take >> this code for example, >> #include <stdexcept> >> void dummysymbol() { >> throw(std::runtime_error("string"));

...tracking compile time in the future, > we'll reach a state where we'll be able to consider "breaking" the > compile-time regression test as important as breaking any test: i.e. the > offending commit should be reverted unless it has been shown to > significantly (hand wavy...) improve the runtime performance. In order to have any kind of threshold, we'd have to monitor with some accuracy the performance of both compiler and compiled code for the main platforms. We do that to certain extent with the test-suite bots, but that's very far from ideal. So, I'...

...signee: nouveau at lists.freedesktop.org Reporter: russianneuromancer at ya.ru QA Contact: xorg-team at lists.x.org Created attachment 123785 --> https://bugs.freedesktop.org/attachment.cgi?id=123785&action=edit photo On laptops with G72M picture on VGA output is always wavy (please look into attached photo). That was tested with two laptops (with 7300 Go and 7400 Go) couple of projectors (800x600) and few displays (up to 1920x1080) - issue is reproducible with any combination with any Linux that was released for latest ~three years (with Linux 4.6 too). Other issue is...

...eople mention on Slashdot that it runs on Wine. I run Debian (woody) on an AMD Athlon 1.4GHz machine with 1Gb RAM as my desktop. It currently has a Voodoo3 video card, though I have a dual head Radeon which I'm going to use once I get a monitor that is compatible (my current monitor has a very wavy display with that card). I installed Debian's Wine packages and went through the half life install without event. Running HL proved to be dreadfully slow. I read the Linux HL faq and wondered whether the Debian Wine was compiled with GL support. I remove the Debian Wine and checked out the CVS...

On 2017-04-26 19:56, Eric Christopher wrote: > That's really weird. I'm quite surprised that the entry block was moved > so much later in the function but haven't had a chance to look more at > it. Probably want to take a look and find out where that's happening and > why. From irc, thegameg helped me find the -enable-shrink-wrap=false, which "fixes" this,

...to the HEAD, not the whole >>>> > history, I think it's feasible. >>>> >>>> Yep, to be clear, I mean one big change to head, not trying to rewrite >>>> history. >>> >>> >>> I think rewriting history is kind of a hand-wavy pipe dream. ;] I'll >>> believe it when I see it. For now, we should stick to what we know we could >>> actually do, and changing head is the only realistic option there. >>> >> >> FWIW - I don't think we even have that power (when it comes to global &...

> On Oct 8, 2014, at 1:55 AM, Renato Golin <renato.golin at linaro.org> wrote: > > On 8 October 2014 05:25, Chris Lattner <clattner at apple.com> wrote: >>> Up until now the thread has been about “formatting”. You suggested renaming >>> every variable in the project! >> >> If that's what it takes. > > If we're still talking about

...tracking compile time in the > future, we'll reach a state where we'll be able to consider > "breaking" the compile-time regression test as important as breaking > any test: i.e. the offending commit should be reverted unless it has > been shown to significantly (hand wavy...) improve the runtime > performance. > > <troll> > With the current trend, the Polly developers don't have to worry > about improving their compile time, we'll catch up with them ;) > </troll> My two largest pet peeves in this area are: 1. We often use fu...

...directbr and comparison against null is undefined. There is some wording about targets possibly allowing use in inline assembly. Is that really the only option? Is there anything a pass can query to see if it is allowed for a target? I don't see anything like that in TTI. I found this hand-wavy post: http://lists.llvm.org/pipermail/llvm-dev/2014-March/071542.html However, that seems to go against the language rules and could break at any time. In particular, what happens if the BasicBlock is optimized away (merged with another block, etc.)? Thanks! -David