similar to: Targeting Bugs for GlusterFS 3.3 Beta 3

Hi, where could one find any LLVM development roadmap for this and perhaps next year? Especially would be interesting to know about * planned features for PS3 Cell processor -- as well as for Wii, Xbox360 CPUs * multithreading in general * possibly coming changes in major versioning and related issues * other interesting featuring comments on current status to above listed items are also

Hi Valery, On Tue, 2007-04-10 at 13:15 +0200, Valery Khamenya wrote: > Hi, > > where could one find any LLVM development roadmap for this > and perhaps next year? About the best "roadmap" we have is the list of enhancements in Bugzilla:

Is it possible to get a premade query for bugs whom have not had activity for 6+ months? There was one as a sticky in the past. Thanks!

Eric Zimmerman wrote: > Chris, > > I'm fine with using JIT, but I'm trying to understand this problem: > 1. My LLVM program does not produce correct results > 2. Using llvm-dis, I disassemble the bytecode to C > 3. I recompile using GCC and the program _works correctly_. > > The only odd thing is when I recompile with GCC, I see these messages: > >

Howdy Wine users! The list of bugs with downloads that haven't been checked on in a while has gotten pretty long (1,359! as of May 6, 2009). If you're a moderate to advanced user of wine, please help by downloading and testing these applications and testing these bugs. Be sure you're using a recent version of wine (1.1.20 or git) and testing in a clean WINEPREFIX. Quick guide: 1)

Chris, I'm fine with using JIT, but I'm trying to understand this problem: 1. My LLVM program does not produce correct results 2. Using llvm-dis, I disassemble the bytecode to C 3. I recompile using GCC and the program _works correctly_. The only odd thing is when I recompile with GCC, I see these messages: pal3.c:195: warning: conflicting types for built-in function `strcmp'

Hi there wine list this is not going to be a request for help as much as it's a request for how I can help the wine developers. I've got some time over the next couple of weeks and a stack of applications I want to see if I can get running under wine. I thought if I started testing a whole bunch of things I might be able to gather some useful test data for the wine developers as a way

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

GlusterFS newbie (less than a week) here. Running GlusterFS 3.2.6 servers on Dell PE2900 systems with four 3.16 GHz Xeon cores and 16 GB memory under CentOS 5.8. For this test, I have a distributed volume of one brick only, so no replication. I have made performance measurements with both dd and Bonnie++, and they confirm each other; here I report only the dd numbers (using bs=1024k). File

Hey james and JMW: Can/Should we schedule a google hangout where james spins up a puppet-gluster based gluster deployment on fedora from scratch? Would love to see it in action (and possibly steal it for our own vagrant recipes). To speed this along: Assuming James is in England here , correct me if im wrong, but if so ~ Let me propose a date: Tuesday at 12 EST (thats 5 PM in london - which i

This error occurs because the "==" comparison operator doesn't allow comparison of ordered and normal factors: /df[df5$close_quarter == as.Date("2011-02-01"),]/ Warning message: In /`[.data.frame`(df, df$close_quarter == as.Date("2011-02-01")/, : Incompatible methods ("Ops.ordered", "Ops.Date") for "==" Why should this be a

It has been a ludicrously long time (over 8 months) since the last stable release of libguestfs. So I'd like to plan a new 1.30 release soon. Please follow-up if there are features / blockers / bugs that need to be addressed for 1.30. As usual, bugs which have "1.30" (without quotes) in the Devel Whiteboard field in Bugzilla are nominated as blockers for the release. You can see

On Mon, 15 Feb 2016, Jakub Jelen wrote: > On 02/12/2016 04:56 AM, Damien Miller wrote: > > Hi, > > > > OpenSSH 7.2 is almost ready for release, so we would appreciate > > testing on as many platforms and systems as possible. This release > > contains many bugfixes and several new features. > Hi there, > > Would it be possible to cover also ssh-copy-id

Hi, First of all, apologies if I'm not posting this in the correct place. I'm successfully running Microsoft Visual Foxpro 7 under Wine, however I needed to use the native versions of shlwapi and oleaut32. There is a major problem still, however, and that is that foxpro will freeze as soon as I use the mouse to click in certain controls (the command window, a textbox, an edit box,

The 1.0 release of Wine is tenatively scheduled for the 15th anniversary of the project (roughly 1 June 2008, if you take Dan Dulitz' message as the start of the project, http://groups.google.com/group/comp.os.linux/msg/7f92abdf494ab8b3 ) Over the last six or so months, the wine developers have identified 180 or so bugs as possibly being worth fixing before the 1.0 release. 63 of the Wine

RPM: http://bits.gluster.org/pub/gluster/glusterfs/3.4.1qa2/ SRC: http://bits.gluster.org/pub/gluster/glusterfs/src/glusterfs-3.4.1qa2.tar.gz This release is made off jenkins-release-42 -- Gluster Build System

On Wed, Oct 26, 2011 at 1:59 AM, Chris Lattner <clattner at apple.com> wrote: > > Fantastic.  A great place to start would be to investigate / screen various sparc related bugs in bugzilla to see if they are still relevant and present: > http://llvm.org/bugs/buglist.cgi?quicksearch=sparc > > This bug looks pretty fatal if it is actually real: >

I think that somebody should update the WINE's TODO list for 1.0.1 All the bugs in the list (http://bugs.winehq.org/buglist.cgi?product=Wine&target_milestone=1.0.1&order=bugs.bug_severity) are closed/fixed. [Rolling Eyes]

Libguestfs 1.34 was released on 2016-08-08, which is about 6 months ago. I'd would like to think about what needs work for the next stable 1.36 release, which might happen at the end of this month. Any new APIs added in the 1.35 cycle will become supported and guaranteed when we release 1.36, so we need to check those. See: git diff v1.34.0 -- generator/actions.ml It looks like there

Hello everyone, According to the release schedule, we're supposed to be tagging 'final' on Wednesday. Unfortunately, I suspect we will be a little late. There are currently 32 open release blockers: https://bugs.llvm.org/buglist.cgi?f1=blocked&o1=equals&v1=33849&query_format=advanced&resolution=--- Some of those have traction, but many don't. Some just need