search for: innocuously

On Tue, Feb 17, 2009 at 2:35 PM, Mike Stump <mrs at apple.com> wrote: > On Feb 17, 2009, at 2:21 PM, Scott Michel wrote: > > - remove trailing whitespace, > > - expand tabs to spaces, > > I'd argue for not changing anything, just fail it. > Trimming whitespace is innocuous, at best. Expanding tabs to spaces, I might be inclined to agree is a 'fail' since

I just noticed that on centso 4.5 I have an executable with the +s (chmod +s myexe) doing a chmod root myexe and chown root myexe does NOT affect the +s setting. However, on centos 5 this is not the case. chmod +s myexe chown root myexe or chgrp root myexe will DROP the +s status. How can I get around this? I want to keep the owner, group, world settings. Thanks, Jerry

I noticed, what seened to me, to be odd. These produce a boxplot in the first case and a spineplot in the second case in R .2.2.0: plot(Sepal.Length ~ Species, iris) plot(Species ~ Sepal.Length, iris) What if one wants to exchange axes? Does the fact that this seemingly innocuous change result in completely different graphics make sense? Is it desirable?

Hi all, Not sure if I''m the only one with this problem... We''re on edge for both rails and rspec, and i just did an update... Some apparently innocuous rails stuff was updated, and then half my specs broke due to an error in rspec_on_rails: ArgumentError in ''UserController without logged in user should show the index page'' wrong number of arguments (2

On Mar 19, 2014, at 11:32 AM, Aaron Ballman <aaron at aaronballman.com> wrote: > On Wed, Mar 19, 2014 at 2:13 PM, Lang Hames <lhames at gmail.com> wrote: >> Hi all, >> >> As RFCs go this is short and sweet - I think it would be nice to add an >> empty method to iterator_range. Something like: >> >> bool empty() const { return begin() != end();

On Friday 26 September 2008 16:59, Chris Lattner wrote: > On Sep 26, 2008, at 8:43 AM, David Greene wrote: > >> Do you have a testcase? It sounds like something that would be easy > >> to fix. > > > > I have a fix (yes, it was trivial). I'll have to see about a > > testcase as it's > > proprietary code. > > Usually, proprietary testcases

Hi, I am working with the package nlme, and I tried creating a new correlation class (which, according to the help pages, is possible if you write a few new method functions). Anyways, I think I am 99% of the way there, but I have a recurring problem with R crashing on seemingly innocuous statements (I have set debug() on nearly every function, so I can see where it is failing). For instance,

Question: I am trying to impliment a function in R that we use quite regularly in Splus, and it fails due to a lack of the "terms.inner" function in R. The substitute is? Part question and part soapbox: Why remove terms.inner from R? It's little used, but rather innocuous. Mostly soapbox: I figured it was no big deal, as I originally discovered the use of terms.inner from

> On 30 Jan 2019, at 9:24 am, Stephan Bosch <stephan at rename-it.nl> wrote: > > > > Op 29/01/2019 om 01:51 schreef James Brown via dovecot: >> I?ve set up a new mail server. Auth-worker is giving me this error all the time: >> >> auth-worker(11160): Info: passwd(sales at bordo.com.au <mailto:sales at

Hi, Can anyone suggest any reasons why this seemingly-innocuous (though stupid-looking) excerpt from gnu fileutils 4.1 would make llvm-gcc go so incredibly slowly? It doesn't seem to be a question of the size of the output. Here's what I do: % time llvm-gcc -c sha24.c 56.840u 0.050s 1:07.05 84.8% 0+0k 0+0io 1050pf+0w % ls -l sha24.o -rw-r--r-- 1 brg brg 5784

"Duncan P. N. Exon Smith" <dexonsmith at apple.com> writes: >> On 2014-Jun-25, at 12:32, Alp Toker <alp at nuanti.com> wrote: >> >> As I understand, some people legitimately use Phabricator for >> internal review, > > Is this is a use case we need to support on <http://reviews.llvm.org>? > >> while others *think* they're

On Thursday 25 September 2008 19:12, Chris Lattner wrote: > On Sep 24, 2008, at 5:11 PM, David Greene wrote: > > I just ran into this today with x86-64: > > > > Cannot yet select: 0x3cbc180: f64 = ConstantFP <1> > > > > As far as I can tell, DAGCombiner comes along and sees an sint_to_fp > > of the > > constant 1 and hapilly folds it into a

On Sep 26, 2008, at 8:43 AM, David Greene wrote: >> >> Do you have a testcase? It sounds like something that would be easy >> to fix. > > I have a fix (yes, it was trivial). I'll have to see about a > testcase as it's > proprietary code. Usually, proprietary testcases can be reduced and simplified to the point where they are innocuous, -Chris

On Sep 29, 2008, at 9:21 AM, David Greene wrote: >> Usually, proprietary testcases can be reduced and simplified to the >> point where they are innocuous, > > Yep, that's what I'm trying to do. Have you run delta?

On Feb 17, 2009, at 2:46 PM, Scott Michel wrote: > Trimming whitespace is innocuous, at best. Unless you're doing a testcase that wants to verify a feature.

Hi All - Ever since I upgraded to 6.8 I have usually been getting a trace back report for some bits related to Nouveau whenever the screensaver has been running and I get back into the system. Along the lines of: :Pid: 31, comm: events/4 Tainted: G W -- ------------ 2.6.32-642.el6.x86_64 #1 :Call Trace: :[<ffffffff8107c911>] ? warn_slowpath_common+0x91/0xe0

On Fri, Nov 17, 2006 at 08:32:02AM -0800, Josh Coalson wrote: > OK, I built on one of the sourceforge machines and made a bunch > more fixes. there are a couple innocuous warnings but the tests > all pass for me. I also checked in changes to the vendor string, > can you try one more time now? Yep, all 7 tests pass now. Yay! Attached is an autogen integration patch: (a) pass -I m4

Has anyone put an eye to my patches*? AFAIK, they're simple and quite innocuous. Sorry to be a bother. (*) http://bugs.xiph.org/show_bug.cgi?id=208 http://bugs.xiph.org/show_bug.cgi?id=210 -- -:-:- David K. Gasaway -:-:- XNS : =David K Gasaway -:-:- Email: dave@gasaway.org -:-:- Web : dave.gasaway.org <p><p>--- >8 ---- List archives: http://www.xiph.org/archives/ Ogg

Hi all, I get a (usually) reproducible error for only one of my controllers. This doesn''t happen for any of the other 10+ controllers. I didn''t see anything weird about file permissions. The "offending" line 142 is quite innocuous and triggers the error even when that portion of the controller is not even being run. . . . 141 while

On 01/08/2014 22:07, Chandler Carruth wrote: > Note that I've fixed one bad compile time regression quite recently, and > we're bisecting to another one. We benchmarked the multithreading stuff > pretty carefully, so I doubt its that. Have you tried reverting locally and > reproducing? Not really. It just saw this passing by and was wondering if it raised some bells. The