search for: r123456

...quest a change be merged to the 3.8 branch. June 1 - Deadline to merge changes to the 3.8 branch. June 1 - 3.8.1-rc1 June 8 - 3.8.1-rc2 (if necessary) June 15 - 3.8.1 Release If you want a patch included in the 3.8.1 release, send an email to llvm-commits with the subject: "3.8 Merge Request: r123456". Make sure to cc me and the code owner. Once you get approval from the code owner and me, then you can merge the patch to the 3.8 branch. If you don't have commit access or are unable to commit the patch, let me know. For the 3.7.1 release, I encouraged people to make stable patch reque...

...if for some reason you are unable to use the script. If you file bugs manually, make sure you mark it as a blocker for the release metabug: 32061 and add a link the commit on phabricator in the url field: e.g http://reviews.llvm.org/rL12345 Description for the bug should be in the form of: Merge r123456 into the 4.0 branch : <80 character commit message summary> * Stable Release Improvements * I would like to start an informal discussion about stable release improvements. My goals for this discussion are to find ways to get more community members/organizations using the official stable r...

On 07/13/2011 05:09 PM, Jay Foad wrote: > I regularly make small API-breaking changes in the name of cleaning > things up. Sorry! I'd be happy to update the release notes if folks > reckon this is the right thing to do. Would it just mean adding a<ul> > to the (currently empty) list in docs/ReleaseNotes.html#api_changes ? That's definitely needed. Not every LLVM user

...rces would be really appreciated. I second that. Preferably all in the same place, in order, with (approx.) revision numbers where it happened. It'd make our jobs much easier to merge our local base with trunk. A simple text would suffice: <li><b>New Type System</b>: As of r123456, the type system is... Uses of ... have been replaced by ..., ... and ... have been deprecated, please use ... instead.</li> cheers, --renato

...reading '-###' output, but it's kind of spewy and I don't think that's the problem. This is what clang -v gives for me: clang version 3.2 Target: x86_64-unknown-linux-gnu Thread model: posix It looks like it wants the version line to be something like the form clang version (r123456) 3.2 or something like that. --Sean Silva On Thu, Sep 6, 2012 at 12:58 AM, David Blaikie <dblaikie at gmail.com> wrote: > On Wed, Sep 5, 2012 at 7:23 PM, Sean Silva <silvas at purdue.edu> wrote: >> Hi, I'm trying to use LNT to run the test-suite. I followed the >>...

On Jan 29, 2013, at 12:11 PM, Nuno Lopes <nunoplopes at sapo.pt> wrote: >> On 01/28/2013 07:45 PM, Tanya Lattner wrote: >>> I will be removing the list prefix "LLVMDev" from the subject line. If you are filtering by this, please use the list headers instead. >>> >>> If you have any questions, please let me know. >> >> Thanks Tanya,

I agree that the list name is redundant and should be dropped, but the revision number is compact and very useful... -Chris On Nov 15, 2012, at 6:45 PM, Tobias Grosser <tobias at grosser.es> wrote: > On 11/16/2012 02:47 AM, Chris Lattner wrote: >> >> On Nov 15, 2012, at 2:28 PM, Chandler Carruth <chandlerc at google.com> wrote: >> >>>>

> On 01/28/2013 07:45 PM, Tanya Lattner wrote: >> I will be removing the list prefix "LLVMDev" from the subject line. If >> you are filtering by this, please use the list headers instead. >> >> If you have any questions, please let me know. > > Thanks Tanya, this makes the subject lines of the commits a lot more > accessible. > > Tobi Please

...; If you file bugs manually, make sure you mark it as a blocker for >> the release metabug: 32061 and add a link the commit on phabricator >> in the url field: e.g http://reviews.llvm.org/rL12345 >> >> Description for the bug should be in the form of: >> >> Merge r123456 into the 4.0 branch : <80 character commit message summary> >> >> >> * Stable Release Improvements * >> >> I would like to start an informal discussion about stable release >> improvements. My goals for this discussion are to find ways to >> get more...

On Wed, Sep 5, 2012 at 7:23 PM, Sean Silva <silvas at purdue.edu> wrote: > Hi, I'm trying to use LNT to run the test-suite. I followed the > instructions on <http://lnt.llvm.org/quickstart.html>. When I run it I > get this error: > > (mysandbox)sean:~/pg/others/llvm % lnt runtest nt --sandbox mysandbox > --cc ~/pg/others/llvm/release/bin/clang --test-suite

Hi, I'm trying to use LNT to run the test-suite. I followed the instructions on <http://lnt.llvm.org/quickstart.html>. When I run it I get this error: (mysandbox)sean:~/pg/others/llvm % lnt runtest nt --sandbox mysandbox --cc ~/pg/others/llvm/release/bin/clang --test-suite test-suite nt.py:1185: note: inferred C++ compiler under test as:

The first release candidate of the 9.1-RELEASE release cycle is now available on the FTP servers for amd64, i386, and powerpc64. The MD5/SHA256 checksums are at the bottom of this message. The ISO images and, for architectures that support it, the memory stick images are available here: ftp://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/9.1/ (or any of the FreeBSD mirror sites). Current

On Wed, Nov 26, 2014 at 10:15:13AM +0000, Daniel Sanders wrote: > > From: Daniel Sanders > > Sent: 25 November 2014 17:39 > > To: Eric Christopher; Tom Stellard > > Cc: LLVM Developers Mailing List (llvmdev at cs.uiuc.edu) > > Subject: RE: [LLVMdev] Proposed patches for Clang 3.5.1 > > > > > > > > I'd also like to propose the inclusion of