From: Pekka Enberg <penberg@kernel.org>
To: Christopher Li <sparse@chrisli.org>
Cc: Jeff Garzik <jeff@garzik.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: suggestion for Merging LLVM
Date: Tue, 13 Dec 2011 22:29:42 +0200 [thread overview]
Message-ID: <1323808182.1428.309.camel@jaguar> (raw)
In-Reply-To: <CANeU7QnXWEFFBsHs4V6Z_Mbpq4R+y=f_Ot5CL95WiE49ehDdOA@mail.gmail.com>
On Fri, Nov 25, 2011 at 12:18 PM, Jeff Garzik <jeff@garzik.org> wrote:
> > According to http://llvm.org/ the release date for 3.0 is November 30,
> > downgrading due to impatience. If Pekka wants to get it going on 2.x I've
> > no objection, but I am lazy and see no reason to do any extra work with 3.0
> > release so close.
On Fri, 2011-11-25 at 12:30 -0800, Christopher Li wrote:
> I will take a look how hard it is hard to support llvm 2.9. Don't know when the
> 3.0 will be available in Fedora.
Ping? LLVM 3.0 is out now officially.
next prev parent reply other threads:[~2011-12-13 20:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-22 2:43 suggestion for Merging LLVM Christopher Li
2011-11-22 5:52 ` Jeff Garzik
2011-11-22 6:01 ` Pekka Enberg
2011-11-22 20:32 ` Jeff Garzik
2011-11-22 20:38 ` Pekka Enberg
2011-11-23 4:11 ` Jeff Garzik
2011-11-23 6:01 ` Jeff Garzik
2011-11-23 6:58 ` Pekka Enberg
2011-11-25 1:45 ` Christopher Li
2011-11-25 2:25 ` Jeff Garzik
2011-11-25 5:52 ` Pekka Enberg
2011-11-25 6:28 ` Christopher Li
2011-11-25 6:43 ` Pekka Enberg
2011-11-25 8:05 ` Christopher Li
2011-11-25 8:29 ` Pekka Enberg
2011-11-25 17:52 ` Jeff Garzik
2011-11-25 19:13 ` Christopher Li
2011-11-25 20:18 ` Jeff Garzik
2011-11-25 20:30 ` Christopher Li
2011-12-13 20:29 ` Pekka Enberg [this message]
2011-12-15 21:34 ` Christopher Li
2011-12-20 8:53 ` Pekka Enberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1323808182.1428.309.camel@jaguar \
--to=penberg@kernel.org \
--cc=jeff@garzik.org \
--cc=linux-sparse@vger.kernel.org \
--cc=sparse@chrisli.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox