search for: ambivalent

...a the mailing list (which has very high volume). I was going to reply that I do post the release announcements on the blog, but now I see I forgot to do that for 3.8 :-/ Last time, I talked about posting to llvm-announce about release candidates, etc., but never actually followed through as I was ambivalent about how people would perceive the signal-to-noise ratio. It's similar for the blog: is info about release candidates valuable for those not involved enough to read llvm-dev, or would it be perceived as noise, hiding more important contents? I'm pretty undecided...

First off, congrats to everyone for getting Rails 2 released. A lot of work went into the release, and it''s good to see us reach this milestone. And now that the release dust has settled, I think it might be useful for us to have a retrospective and evaluate how the release went. I think the Ruby on Rails project has improved a lot this year, and this is another opportunity

...o substantial speedups. It''s certainly possible that the problems I saw were my own bugs, or the result of passing the wrong parameters to ferret methods, which I''ve had problems with before... I''ll keep trying and do a big test overnight, but so far, the news is..... ambivalent. As far as the 64-bit warnings go, most are now gone, with one exception: r_search.c: In function ''frt_td_to_s'': r_search.c:202: warning: format ''%d'' expects type ''int'', but argument 3 has type ''long int'' Dave, I''...

I made some progress this afternoon. I now have a set of changes in my local sandbox that allows clang to pass all of the tests in the suite I’ve been using to exercise this code. How do you feel about working these changes into trunk to establish a working baseline, even knowing that parts of this are going to be redesigned? -Andy From: Reid Kleckner [mailto:rnk at google.com] Sent:

Hi all, I''ve been looking at the performance of my fb app and one glaring issue seems to be with the parsing speed of rexml in processing the results. Has anyone looked into porting the facebooker parser from rexml to libxml? If not, any reason I shouldn''t try? Thanks! Yu-Shan. -------------- next part -------------- An HTML attachment was scrubbed... URL:

I thought this made sense, but apparently I am mistaken: define copyfile($owner = root, $group = root, $repo = "config", $mode, $source = $name, $purge = false, $backup = false, $recurse = false, $server = $servername) { file { $name: mode => $mode, owner => $owner, group => $group, backup => $backup,

...sonably confident that it can't > possibly be correct. The Xen PV ABI only has a single kernel stack pointer which may be registered. There is no equivalent of an IST, so if a second fault occurs, it is delivered normally on the current stack. By the looks of it, the other NMI handling is ambivalent to the fact that it isn't really on an IST stack under Xen. ~Andrew

...sonably confident that it can't > possibly be correct. The Xen PV ABI only has a single kernel stack pointer which may be registered. There is no equivalent of an IST, so if a second fault occurs, it is delivered normally on the current stack. By the looks of it, the other NMI handling is ambivalent to the fact that it isn't really on an IST stack under Xen. ~Andrew

defines.h defines a bunch of IPTOS constants if they're not already available: #ifndef IPTOS_LOWDELAY # define IPTOS_LOWDELAY 0x10 # define IPTOS_THROUGHPUT 0x08 # define IPTOS_RELIABILITY 0x04 # define IPTOS_LOWCOST 0x02 # define IPTOS_MINCOST IPTOS_LOWCOST #endif /* IPTOS_LOWDELAY */ A few lines further down, it includes <netinet/ip.h>, which

...lt;mst at redhat.com> Date: Wed, 15 Oct 2014 16:23:28 +0300 > You used __netif_subqueue_stopped but that seems to use > a slightly more expensive test_bit internally. More expensive in what sense? It should be roughly the same as "x & y" sans the volatile. Anyways I'm ambivalent and I want to see this bug fixes, so I'll apply your patch. Thanks!

commit 0b725a2ca61bedc33a2a63d0451d528b268cf975 net: Remove ndo_xmit_flush netdev operation, use signalling instead. added code that looks at skb->xmit_more after the skb has been put in TX VQ. Since some paths process the ring and free the skb immediately, this can cause use after free. Fix by storing xmit_more in a local variable. Cc: David S. Miller <davem at davemloft.net>

commit 0b725a2ca61bedc33a2a63d0451d528b268cf975 net: Remove ndo_xmit_flush netdev operation, use signalling instead. added code that looks at skb->xmit_more after the skb has been put in TX VQ. Since some paths process the ring and free the skb immediately, this can cause use after free. Fix by storing xmit_more in a local variable. Cc: David S. Miller <davem at davemloft.net>

nowhere does it say that centos is approved for use in DoD. it is not on the APL, only RedHat and SuSE

...ce controller. I''d actually slowed down this time to think about what I was doing in hopes of automating the task. I''ve tended to use script/generate rspec_scaffold to get the skeleton set of specs along with the model, migration, controller views, etc. I''ve been a bit ambivalent about this, for one thing if feels a little un-bdd to have the specs generated, but on the other hand the code tends to be so pro-forma (at least to start out) and the generate specs help as a regression check, and to help me think about how and whether to deviate from things like flows between bro...

...from hw/virtio/virtio-pci.c:24: include/hw/virtio/virtio-access.h: In function ?virtio_access_is_big_endian?: include/hw/virtio/virtio-access.h:28:15: error: attempt to use poisoned "TARGET_WORDS_BIGENDIAN" #elif defined(TARGET_WORDS_BIGENDIAN) ^ FWIW when I added endian ambivalent support to virtio, I remember *some people* getting angry at the idea of turning common code into per-target... :) See comment below. > Signed-off-by: Cornelia Huck <cornelia.huck at de.ibm.com> > --- > hw/block/dataplane/virtio-blk.c | 3 +- > hw/scsi/virtio-scsi-datapl...

...from hw/virtio/virtio-pci.c:24: include/hw/virtio/virtio-access.h: In function ?virtio_access_is_big_endian?: include/hw/virtio/virtio-access.h:28:15: error: attempt to use poisoned "TARGET_WORDS_BIGENDIAN" #elif defined(TARGET_WORDS_BIGENDIAN) ^ FWIW when I added endian ambivalent support to virtio, I remember *some people* getting angry at the idea of turning common code into per-target... :) See comment below. > Signed-off-by: Cornelia Huck <cornelia.huck at de.ibm.com> > --- > hw/block/dataplane/virtio-blk.c | 3 +- > hw/scsi/virtio-scsi-datapl...

...(or at least do a lot of them) the explicit anchors in an attempt to make LLVM -Wweak-vtables clean but never got around to going all the way there. I think Chris Lattner even advocated for not out-of-lining dtors just to make the vtables strong, instead using an explicit anchor. But I'm pretty ambivalent about it. In theory the style guide advocates this for build perf reasons - which would be interesting to test & see if it's actually relevant. If it's a matter of correctness/functionality as this thread seems to imply (but I haven't read it enough to really understand what's b...

https://bugzilla.mindrot.org/show_bug.cgi?id=2606 Bug ID: 2606 Summary: IPv6 bind address vs autoconfiguration privacy Product: Portable OpenSSH Version: -current Hardware: Other OS: Linux Status: NEW Severity: enhancement Priority: P5 Component: ssh Assignee: unassigned-bugs

Hi, I''m just starting out with Scriptalicious + Prototype, and I''ve run into a problem. I''m trying to create an Ajax.InPlaceEditor that combines the custom size textbox, and the custom parameter (from the examples in the scriptalicious documentation) http://github.com/madrobby/scriptaculous/wikis/ajax-inplaceeditor I''ve tried a couple different methods (one of

Hello Wouter, We used tinydns for many years. After migration to nsd3 we miss only one feature present in tinydns only: tinydns may switch addresses by decreasing the ttl for old data and serve new data starting from a fixed timestamp. http://cr.yp.to/djbdns/tinydns-data.html: You may include a timestamp on each line. If ttl is nonzero (or omitted), the timestamp is a starting time for the