similar to: [LLVMdev] New, incremental, approach to release notes

Hi All, With 2.9 starting to make its way out into the world, it is time to start poking at the release notes. I plan to make a pass through llvm-commits to cull some of the major changes into bullets, but am already behind and insanely busy with other stuff over the next week. If you have commit access, I'd really appreciate it if you could take a pass through llvm/docs/ReleaseNotes.html

I wrote a rexml script that parses rather big xml files (DOM parsing) and builds an object out of them. This is what it looks like after i parse the xml file and display the object: [#<Article:0xb79e7428 @brand="This is a story from ", @id=5337, @fblurb="burb", @ntype="news type here", @copy="Copyright \302\251 2006 ", @source="source",

On 11.05.2012, at 22:55, Bill Wendling wrote: > Hi all! > > Please remember to update the release notes! We're getting close to the release date, and we need the notes to be up-to-date. I added some bigger picture notes to http://llvm.org/docs/ReleaseNotes.html this morning, but we're still missing a lot of text, specifically: - clang: clang has it's own release notes

The first draft of the LLVM 3.0 release notes now done, in llvm/docs/ReleaseNotes.html (the web page isn't autoupdating at the moment). Please take a look and make corrections or enhancements as you see fit. There are still a few things that I need from specific people (marked with XXX's): - BillW is writing a blog about exception handling. - The llvm.expect intrinsic isn't documented

Internal API changes mentioned the Type system changes twice... merging. It should now read: The biggest and most pervasive change is that the type system has been rewritten: PATypeHolder and OpaqueType are gone, and all APIs deal with Type* instead of const Type*. If you need to create recursive structures, then create a named structure, and use setBody() when all its elements are built. Type

The LLVM 3.2 release is winding down, and that means release notes! There are two pieces to this. First, if you're an external LLVM user, we'd like to list you as such in the release notes. This is a great way to get some free advertisement. The section is here: http://llvm.org/viewvc/llvm-project/llvm/branches/release_32/docs/ReleaseNotes.html?revision=HEAD#externalproj Please email

Sorin, I recommend you stick to Transmission since it's in Base. I have however issued updated packages for Deluge in my nux-dextop repo if it helps you. Also check rtorrent out. HTH Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro ----- Original Message ----- > From: "Sorin Srbu" <Sorin.Srbu at orgfarm.uu.se> > To: "(centos at

Hi all! Please remember to update the release notes! We're getting close to the release date, and we need the notes to be up-to-date. Also, if you have a project which uses LLVM, please send me a blurb about it and I can add it to our "external projects" list (or, if you have commit access, you can add it). Thanks! -bw

Hey, Do you want projects which specifically use LLVM 3.1 or just LLVM in general? Regards, Alex On Fri, May 11, 2012 at 10:55 PM, Bill Wendling <wendling at apple.com> wrote: > Hi all! > > Please remember to update the release notes! We're getting close to the release date, and we need the notes to be up-to-date. > > Also, if you have a project which uses LLVM, please

Hi all, Just switched my home computer from Windows 7 to CentOS 6.6 and I'm having a slight bit of trouble with the bittorrent-clients. * Transmission is fine but lacks "a bit" in features. * Vuze is my preferred bt-client but gives me horrendous gfx-artifacts, like not showing the torrent name (it's white text on a white background or some such...). * Deluge is better, and

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Just wondering to myself: What made you switch from Windows 7 to CentOS 6.6? Eliezer On 12/28/2014 10:36 AM, Sorin Srbu wrote: > Hi all, > > Just switched my home computer from Windows 7 to CentOS 6.6 and I'm > having a slight bit of trouble with the bittorrent-clients. > > * Transmission is fine but lacks "a bit"

It seems anyone posting to this list gets a deluge (and I mean a deluge) of virus infected windows garbage. It's basically enough to ruin any email address you sign up to the list with; it doesn't matter if you have a virus scanner integrated with your MTA, I really don't want to see 200 virus notifications a day because i posted to this list. I have been getting about 20MB of swen a

Josh Coalson <xflac@yahoo.com> wrote: > thanks for the patch. No prob :) > also, if you have miroslav's patch again a more updated version > of bitbuffer.c that would be great. I have been meaning to get > around to applying it for a long time. This is Miroslav's patch, from the mailing list post I dug up in the archives: --- orig/src/libFLAC/bitbuffer.c +++

Hello! A few days ago I received a filesystem memory corruption notification from Debian's Linux kernel (2.6.20), which automatically unmounted my root partition. Upon closer investigation, I found that something had overwritten most of my data, XFS's superblocks and other metadata structures. That means from partition offset 0x200. At the time of the error, the only services I was using

Ok, here is a patch waiting for new CVS :). It works fine for me, but please check it before commiting... -- Miroslav Lichvar -------------- next part -------------- --- src/libFLAC/bitbuffer.c.orig 2003-01-30 17:36:01.000000000 +0100 +++ src/libFLAC/bitbuffer.c 2003-01-30 21:53:18.000000000 +0100 @@ -51,6 +51,25 @@ */ static const unsigned FLAC__BITBUFFER_DEFAULT_CAPACITY = ((65536 - 64) *

Oh yeah, if you are working on a problem that works with 2.7, please send me a(n updated) blurb for the "External Open Source Projects Using LLVM 2.7" section, thanks! -Chris

Hi All, If you have an out of tree project that works with the 2.9 release, and would like to be mentioned here: http://llvm.org/docs/ReleaseNotes.html#externalproj please send me a blurb ASAP. -Chris

I wrote a rexml script that parses rather big xml files (DOM parsing) and builds an object out of them. This is what it looks like after i parse the xml file and display the object: [#<Article:0xb79e7428 @brand="This is a story from ", @id=5337, @fblurb="burb", @ntype="news type here", @copy="Copyright \302\251 2006 ", @source="source",

Hello, Thought I''d pass this along to any job seekers out there. My understanding is that this is a relatively junior to mid-level position. ============================================================== Web Application Developer -- Ruby on Rails Blurb, Inc, San Francisco (Full Time) Are you a person who is excited to explore new technologies and build cutting edge applications

Ok, the LLVM 2.7 release notes are in near final shape. Please take a look and suggest improvements (or, better yet, just commit improvements if you have commit access): http://llvm.org/docs/ReleaseNotes.html Things still needed are marked with FIXMEs. These include: 1. Clang needs a blurb describing what's new in 2.7. Have the clang folks been doing anything for the last 6 months? 2. I