search for: unanimously

On Aug 25, 2009, at 1:04 AM, Albert Graef wrote: > . For many applications > other than LLVM itself, the basic LLVM <=2.5 interface which just > overwrites existing files is all that's ever needed. On LLVM trunk, raw_fd_ostream is now back to overwriting files by default, as it is the unanimous preference among in-tree users (and out-of-tree users that I'm aware of). Dan

Smooth review. The case was approved unanimously by the members present. This is the summary of actions: . Advice to the team to follow on issue djr-02, clarifying the rationale for -p vs -a. . TCR - Add a format specifier (e.g. -F gnuplot) to show-usage . Two spec updates: - EOF of the VLAN PPA hack removal - Clarify mac_intr_t . O...

I want to install smarmontools v 5.40, and so I pulled the SRPM for 5.39 so I could patch and install... $ wget -Nc ftp://ftp.redhat.com/pub/redhat/linux/enterprise/6Workstation/en/os/SRPMS/smartmontools-5.39.1-2.el6.src.rpm However, the install of the source fails. $ rpm -ivh smartmontools-5.39.1-2.el6.src.rpm warning: smartmontools-5.39.1-2.el6.src.rpm: V3 RSA/MD5 signature: NOKEY, key ID

FYI, our usual recommendation is to use clang-format only on changed code, unless there's strong evidence that the cost of the initial reformatting is basically zero (which usually means a team / community is pretty unanimous about the decision). On Thu, Jan 9, 2014 at 11:53 AM, Tobias Grosser <tobias at grosser.es> wrote: > Manuel, Daniel, > > I forgot to CC you in this

Isn't cached swap somewhat an oxymoron? Why cache virtual? Am I misunderstanding this line from top? Swap: 524120k total, 80760k used, 443360k free, 73448k cached Mike -- p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);} Oppose globalization and One World Governments like the UN. This message made from 100% recycled bits. You have found the bank of Larn.

...enarios ... http://fixture-scenarios.googlecode.com/svn/trunk/fixture_scenarios ...into a project with some RSpec specifications. They all went kablooey. I didn''t even create a scenario; the system just started calling its version of fixtures(). The normal tests pass and the RSpec ones unanimously emit: TypeError in ''Context (verbose situation...)'' can''t convert nil into String ..lib/fixture_scenarios.rb:108:in `open'' ..lib/fixture_scenarios.rb:108:in `read_fixture_files'' ..lib/fixture_scenarios.rb:66:in `initialize'' ..lib/fixture_scena...

Given this example #start code a<-c(0,70,50,100,70,650,1300,6900,1780,4930,1120,700,190,940, 760,100,300,36270,5610,249680,1760,4040,164890,17230,75140,1870,22380,5890,2430) b<-c(0,0,10,30,50,440,1000,140,70,90,60,60,20,90,180,30,90, 3220,490,20790,290,740,5350,940,3910,0,640,850,260) wilcox.test(a, b, paired=FALSE) #sum of rank for first sample sum.rank.a <-

Hello Everyone, 3 weeks back we (most of the maintainers of Gluster projects) had a meeting, and we discussed about features required for Gluster 4.0 and also the possible dates. <https://hackmd.io/GwIwnGBmCsCM0FoDMsAcBTBAWADLLCYATLJiOmBVgMYAmAhvbLUA#summary> Summary: - It is agreed unanimously that the Gluster 4.0 should be feature based release, and not just time based. - The discussions were on what are the blocking features for 4.0 release, and below were some features which we are considering as blocker for release. - *glusterd2*: The scalable management inte...

I asked before (about 2 weeks) about this, and was told it was in testing. I wonder when it will be available. My GF is considering leaving Debian due to it not recognizing her hardware very well, and I thought a CentOS 5 LiveCD might be a reasonable way for her to see whether CentOS might do a better job. If no LiveCD is forthcoming soon, then I'll burn a copy of the CentOS 4 LiveCD and let

On bootup, it seems CentOS automatically mounts the floppy drive to /media/floppy. Is there a way to stop this from happening, short of removing the floppy drive from the system (as I don't use it)? Thanks, Ash Christopher -------------- next part -------------- An HTML attachment was scrubbed... URL:

On Tue, Feb 18, 2020 at 2:55 AM David Chisnall via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hi Tanya, > > On 18/02/2020 00:56, Tanya Lattner wrote: > > I understand not everyone wants to use Google docs which was why I gave > an option to reply via email as well. My intention on using Google docs is > really just based on my experience using it for docs that span

It's that time again ? we want to test the GlusterFS 3.4 beta before we unleash it on the world. Like our last test fest, we want you to put the latest GlusterFS beta through real-world usage scenarios that will show you how it compares to previous releases. Unlike the last time, we want to focus this round of testing on Infiniband and RDMA hardware. For a description of how to do this, see

...the maintainers of Gluster projects) had a > meeting, and we discussed about features required for Gluster 4.0 and also > the possible dates. > > <https://hackmd.io/GwIwnGBmCsCM0FoDMsAcBTBAWADLLCYATLJiOmBVgMYAmAhvbLUA#summary> > Summary: > > - > > It is agreed unanimously that the Gluster 4.0 should be feature based > release, and not just time based. > - > > The discussions were on what are the blocking features for 4.0 > release, and below were some features which we are considering as blocker > for release. > - *glusterd2*:...

I am considering installing CentOS 4.4, and am interested in how best to set up. I have been using FC2 and helping administer a Debian machine for a few years, but do not consider myself a Linux guru. My current set up uses a /swap partition which is 2x my memory size mem = 256 MB $ sudo /sbin/fdisk -l /dev/hda6 76506 77545 524128+ 82 Linux swap I'm interested in the

Thanks for everyone giving their feedback! I saw pretty unanimous support for making -mcpu=generic the default and making -mcpu=generic schedule for an in-order CPU (Cortex-A8 in this case). I'll be making those changes shortly. I think the comments also make clear that it's less obvious whether we'd want -mcpu=native to become a default. It's probably good for some use cases, but

> On Feb 17, 2020, at 10:06 AM, David Chisnall via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hi Tanya, > > Is there a reason for hosting things for review on Google Docs? We currently have both Phabricator and GitHub that work for review of any text-based format. When I click on a Google Docs link, I am asked to agree to a privacy policy that is very vague and I am

Currently we have RH7.3 with compiler gcc 2.96.x My mission, should I choose to accept it, involves moving our embedded application to CentOS 4.1 with gcc 3.x Problem is that about 1/2 million lines of code that gcc 2.96 accepts gives fatal fits to the gcc 3.x compiler from CentOS 4.1 I don't know how many fatal fits, as some disguise others etc. "Can't find register to

Óscar Fuentes wrote: > The changes are not trivial, as for instance llvm::raw_fd_ostream > without flags fails if the file exists, but std::ofstream does not. The > changes include using new names for flags that already exist on the > standard namespace (F_Force instead of O_TRUNC, etc). Also, each of LLVM <=2.5, 2.6 and 2.7(svn) provide their own, incompatible llvm::raw_fd_ostream

Dan Gohman wrote: > > On Aug 25, 2009, at 1:04 AM, Albert Graef wrote: >> . For many applications >> other than LLVM itself, the basic LLVM <=2.5 interface which just >> overwrites existing files is all that's ever needed. > > On LLVM trunk, raw_fd_ostream is now back to overwriting files by > default, as it is the unanimous preference among in-tree users

After fixing some warnings (see prior commits), we can now enable them in configure.ac. --- m4/guestfs_c.m4 | 13 +++---------- 1 file changed, 3 insertions(+), 10 deletions(-) diff --git a/m4/guestfs_c.m4 b/m4/guestfs_c.m4 index e91446f..7250294 100644 --- a/m4/guestfs_c.m4 +++ b/m4/guestfs_c.m4 @@ -43,22 +43,15 @@ fi dnl This, $nw, is the list of warnings we disable. nw= nw="$nw