search for: fickle

instead of sed'ing the exact commented line we are looking for, simply add the necessary lines to the end of the anyterm sysconf --- scripts/ovirt-functions | 9 ++++----- 1 files changed, 4 insertions(+), 5 deletions(-) diff --git a/scripts/ovirt-functions b/scripts/ovirt-functions index af3a257..1c7b0c4 100644 --- a/scripts/ovirt-functions +++ b/scripts/ovirt-functions @@ -213,11

instead of sed'ing the exact commented line we are looking for, simply add the necessary lines to the end of the anyterm sysconf --- scripts/ovirt-functions | 9 ++++----- 1 files changed, 4 insertions(+), 5 deletions(-) diff --git a/scripts/ovirt-functions b/scripts/ovirt-functions index af3a257..98e88e7 100644 --- a/scripts/ovirt-functions +++ b/scripts/ovirt-functions @@ -213,11

...e and adding new tests cheaper, and won't prevent you from also > having windows-specific tests that may use an expanded vocabulary. > > What do you think? > -- adrian > I understand the desire to keep them as similar as possible, but I'm still not really sold that massaging fickle text output into a different text format is going to make things more scalable. I'd like there to be as few layers of text processing as possible. If someone files a bug report that includes a WinDbg command log, I'd like to be able to paste those statements into a test. I also expect th...

...rovide these values over some X extension". This is even more effort now that modesetting is in the kernel (back when nvtv was written, it wasn't). Without this, you are pretty much stuck with precalculated modes. Which isn't optimal, because with small overscan the timing gets a bit fickle, and with larger overscan you get the ugly border, and every analog TV is different in that respect. - Dirk

...This is even more effort now that modesetting is in the kernel (back > > when nvtv was written, it wasn't). > > > > Without this, you are pretty much stuck with precalculated modes. > > Which isn't optimal, because with small overscan the timing gets a bit > > fickle, and with larger overscan you get the ugly border, and every > > analog TV is different in that respect. > > I actually checked this out last night, grabbed the BT869 datasheet. > Basically you'd have to implement something similar to the ch7006 > driver (see drivers/gpu/drm/...

...Similarly, '5.0G' turned into '5 GiB'. Update expected test output to tolerate either version of qemu. Signed-off-by: Eric Blake <eblake@redhat.com> --- I already know I want to send a v2; on IRC, Rich pointed out that 'qemu-img info --output=json' is less prone to fickle changes, and we already depend on jq elsewhere in the testsuite. But since I'd already got this written up, I'm at least posting it (if nothing else, to have a list archive to point to when someone else complains about qemu-img changing output). tests/test-ip.sh | 4 ++-- tests/...

...n),NoOp(open) exten => s,n,WaitExten(0.5); exten => s,n,Set(TIMEOUT(digit)=10) exten => s,n,Set(TIMEOUT(response)=15) exten => s,n,Background(cassandra/NextRep) ****This is the line where I have a problem with dialing an extension. The timing is very fickle and heaps of our callees cannot get to the right extension properly. exten => s,n,WaitExten(10,m[default]) exten => s,n,Macro(dial-us) exten => s,n,Macro(hangupcall) exten => i,1,Playback(pbx-invalid) exten => i,2,Goto(s,open) exten => t,1,Macro(hangupcall) exten => #,1,Macr...

Hi all.. Im using ABE C3.2.1 version and here Im having the following issue with respect to T38 fax calls. Somehow asterisk when it receives Session modification request with the T38 Codec, is not forwarding the request to the other end. Also asterisk is responding with 200 Ok to this RE INVITE with an audio line rather an media line with image. The session id here strangely matches to that of

> ?agrep > Results in: No documentation for 'agrep ' in specified packages and libraries: you could try 'help.search("agrep ")' There is white space after agrep, that ? doesn't ignore. --please do not edit the information below-- Version: platform = i486-pc-linux-gnu arch = i486 os = linux-gnu system = i486, linux-gnu status = major = 2 minor =

...xtension". > > This is even more effort now that modesetting is in the kernel (back > when nvtv was written, it wasn't). > > Without this, you are pretty much stuck with precalculated modes. > Which isn't optimal, because with small overscan the timing gets a bit > fickle, and with larger overscan you get the ugly border, and every > analog TV is different in that respect. I actually checked this out last night, grabbed the BT869 datasheet. Basically you'd have to implement something similar to the ch7006 driver (see drivers/gpu/drm/i2c), which provides an A...

Hello, I have here a GeForce 2MX (NV10) with a Brooktree BT869 chip for the TV-Out. Is the TV-Out on this card supported by Nouveau? I read on the feature matrix something that the TV-Out is only supported for some Chrontel chips, furthermore xrandr -q shows me only the DVI connection (in fact it's VGA, not DVI), but not the S-Video connection. If not supported, is this planned for future

I'm increasingly getting to be of the opinion that the current timeout behaviour of the menu system is ridiculous. I did it this way because someone on this list had expressed concern that serial port glitches would trigger a character which then would cause the thing to sit indefinitely. Well, first of all, such an automatic system would hardly use the menu system, and second of all, I

...gt; The character in your email as received here is an ASCII space, and that is >>> used to end the token on all my systems. That's not to say that you didn't >>> type something else that looks like a space (e.g. a nbspace) since email >>> systems are fickle. >>> >>> None of my guesses worked, so we need precise reproduction instructions. >>> >>> On Thu, 29 May 2008, rocket at google.com wrote: >>> >>>>> ?agrep >>>>> >>>> >...

...` is able to override the output of `llvm-link`), > and it doesn't have a disconnect between `hasFnAttribute()` > and `getAttributes().hasAttribute(FunctionIndex)`. > > Awkwardly, having written that out, I'm kind of leaning toward > it myself right now (maybe I'm fickle?) -- it seems to have > fewer limitations. The main thing I prefer about my proposal > is that it's easier to change the default attributes when > modifying an assembly file by hand, but I suppose we could > write a tool for that? > I think the tool approach deserves a bit of a...

...ffort now that modesetting is in the kernel (back >> > when nvtv was written, it wasn't). >> > >> > Without this, you are pretty much stuck with precalculated modes. >> > Which isn't optimal, because with small overscan the timing gets a bit >> > fickle, and with larger overscan you get the ugly border, and every >> > analog TV is different in that respect. >> >> I actually checked this out last night, grabbed the BT869 datasheet. >> Basically you'd have to implement something similar to the ch7006 >> driver (s...

it's funny. I only started this so my ex-girlfriend on the other side of the world could hear a song (downloading mp3's was not possible for complex reasons but streaming audio was) but goddammit i'm going to make this thing work if it kills me. At 07:29 PM 4/5/2001 -0700, Jack Moffitt wrote: >On Thu, Apr 05, 2001 at 06:21:37PM -0700, William Goldsmith wrote: >> > why

Hi Duncan, Been thinking about this a bit and a few comments/questions. I may have misunderstood some things in your mail though so please feel free to explain at me :) > Changing `clang` to store target defaults on the module will allow us to > continue to override them when running `llc`. The right precedence > would be: > > 1. Explicit attributes set on the function. >

...e the output of `llvm-link`), >> and it doesn't have a disconnect between `hasFnAttribute()` >> and `getAttributes().hasAttribute(FunctionIndex)`. >> >> Awkwardly, having written that out, I'm kind of leaning toward >> it myself right now (maybe I'm fickle?) -- it seems to have >> fewer limitations. The main thing I prefer about my proposal >> is that it's easier to change the default attributes when >> modifying an assembly file by hand, but I suppose we could >> write a tool for that? >> > > I think the tool...

Hi, Has anyone seen this before? The phones are registered OK, and they can take incoming calls, but all I get is a fast busy whatever I dial. I've tried regular numbers, *98, etc. Looking at the Asterisk Command Line Interface, I don't see any text outputted when I try to dial out. I wonder if it's even getting to the Asterisk server. Where does it get the fast busy from--inside

Hi all, I''m a software developer from New Zealand. I''ve built a couple of rails sites and have some ajax experience. I''d like to develop on a rails site with the aim of making a business - is anyone else looking to do the same? The two rails sites I built recently are foopad.com and friendr.com. Regards, Ben