search for: tidious

...ns. FreeBSD has followed the LLVM/Clang releases and backported various fixes locally. NetBSD will after the 3.4 release likely end up doing the same. In the past, this process has created some fragmentation for GCC as various changed tended to accumulate over time. One part was always the somewhat tidious process of getting those changes upstream, the other problem was the difficulty of keeping track of who exactly had what state. Luckily with LLVM we are in much better position when it comes to getting changes integrated, so that's not an issue. There is still the problem of keeping track of w...

...sed to have nice plots in a pdf device are giving awful outputs with the other devices... Playing with the resolution, for instance, impacts directly on the width of lines and sympbols, making them almost invisible at high resolution. Optimizing all these settings for every devices might be very tidious for me, given the number and the length of my scripts. Is there any easy way to keep the aspect of my plots the same way using different devices ? Thanks you in advance for your feedback. Sebastien

...releases and backported various fixes > > locally. NetBSD will after the 3.4 release likely end up doing the same. > > In the past, this process has created some fragmentation for GCC as > > various changed tended to accumulate over time. One part was always the > > somewhat tidious process of getting those changes upstream, the other > > problem was the difficulty of keeping track of who exactly had what > > state. > > > > Luckily with LLVM we are in much better position when it comes to > > getting changes integrated, so that's not an issue...

...owed the LLVM/Clang releases and backported various fixes > locally. NetBSD will after the 3.4 release likely end up doing the same. > In the past, this process has created some fragmentation for GCC as > various changed tended to accumulate over time. One part was always the > somewhat tidious process of getting those changes upstream, the other > problem was the difficulty of keeping track of who exactly had what > state. > > Luckily with LLVM we are in much better position when it comes to > getting changes integrated, so that's not an issue. There is still the >...

...ted various fixes > > > locally. NetBSD will after the 3.4 release likely end up doing the same. > > > In the past, this process has created some fragmentation for GCC as > > > various changed tended to accumulate over time. One part was always the > > > somewhat tidious process of getting those changes upstream, the other > > > problem was the difficulty of keeping track of who exactly had what > > > state. > > > > > > Luckily with LLVM we are in much better position when it comes to > > > getting changes integrated, s...

...t; > > > locally. NetBSD will after the 3.4 release likely end up doing the same. > > > > In the past, this process has created some fragmentation for GCC as > > > > various changed tended to accumulate over time. One part was always the > > > > somewhat tidious process of getting those changes upstream, the other > > > > problem was the difficulty of keeping track of who exactly had what > > > > state. > > > > > > > > Luckily with LLVM we are in much better position when it comes to > > > > gett...

Greetings, We use a dedicated samba-3.3.12+cups-1.3.11 on debian lenny to serve printing (with point and print) to windows clients. We're getting complaints that some clients (win7, vista, XP) have to wait an awful long time from when they hit 'print' to when the job starts coming out of the printer. Other clients (win7, vista, XP) print right away. I can tail the cups log and