search for: release_31

Hi Anton, git-svn got confused at the branch point for the release_31: I see that the current release_31 branch has been created on r155051 as a copy of r155050 from trunk, and r155050 is actually removing an older release_31 branch: Revision 155050 Author: void Date: Wed Apr 18 16:38:33 2012 CDT (11 days, 20 hours ago) Log Message: Removing old release_31 branch...

FYI, I have been maintaining my own release_31 manually on github.com/chapuni. 2012/5/1 Sebastian Pop <spop at codeaurora.org>: > Hi Anton, > > git-svn got confused at the branch point for the release_31: I see > that the current release_31 branch has been created on r155051 as a > copy of r155050 from trunk, and r155050 i...

On Sun, May 6, 2012 at 10:20 AM, NAKAMURA Takumi <geek4civic at gmail.com> wrote: > FYI, I have been maintaining my own release_31 manually on github.com/chapuni. > Thanks for the pointer. I was waiting for Anton to fix the llvm.org git repo for the 3.1 branch. Anton, could you please try to fix the release_31 git branch? Thanks, Sebastian > 2012/5/1 Sebastian Pop <spop at codeaurora.org>: >> Hi Anton, &...

...ranches/*:refs/remotes/branches/*" This is exactly what was done on llvm.org. Here is an example fron clang.git: fetch = trunk:refs/heads/master tags = tags/{RELEASE_20,RELEASE_21,RELEASE_22,RELEASE_23,RELEASE_24,RELEASE_25,RELEASE_26,RELEASE_27,RELEASE_28,RELEASE_29,RELEASE_30,RELEASE_31}:refs/heads/svn-tags/* branches = branches/{release_20,release_21,release_22,release_23,release_24,release_25,release_26,release_27,release_28,release_29,release_30,release_31}:refs/heads/* -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg Sta...

Hi Anton, On Thu, Apr 26, 2012 at 4:05 PM, Anton Korobeynikov <anton at korobeynikov.info> wrote: > Sebastian, > >> I just saw that the git branch remotes/origin/release_31 has been created >> for llvm.  Unfortunately it is missing the right context: right now I can only >> see 11 patches in that branch with the last patch having no parent. >> >> Could somebody please fix this? > This looks like git-svn bug. If anyone knows "the cure&qu...

Hi, I just saw that the git branch remotes/origin/release_31 has been created for llvm. Unfortunately it is missing the right context: right now I can only see 11 patches in that branch with the last patch having no parent. Could somebody please fix this? Thanks, Sebastian -- Qualcomm Innovation Center, Inc is a member of Code Aurora Forum

>> Anton, could you please try to fix the release_31 git branch? > Sorry for late response - I was afk. Given that I received no > complains about clang.git I will switch llvm.git soon :) llvm.git should be sane -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

...ProjObjRoot variable. Stop. make[2]: Leaving directory `/home/abuild/rpmbuild/BUILD/llvm/stage1/projects/compiler_rt' make[1]: *** [all] Error 1 make[1]: Leaving directory `/home/abuild/rpmbuild/BUILD/llvm/stage1/projects' make: *** [all] Error 1 Interestingly trunk works fine but not the release_31 branch. Regards, ismail -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120417/31b50cb9/attachment.html>

Hi All, I was checking for GIT or SVN versions corresponding to llvm3.1 release by checking svn and git logs, but failed to find the exact match. I checked with r156747, which is the last version it shows in      http://llvm.org/svn/llvm-project/llvm/tags/RELEASE_31/ but when I 'diff' this with the 'downloaded llvm3.1 release'(http://llvm.org/releases/download.html#3.1), then I get a lot of differences. (i have excluded .svn directory, .git and some other files during diff) Version 'r155051' logs about creating new directory for '...

...> make[2]: Leaving directory `/home/abuild/rpmbuild/BUILD/llvm/stage1/projects/compiler_rt' > make[1]: *** [all] Error 1 > make[1]: Leaving directory `/home/abuild/rpmbuild/BUILD/llvm/stage1/projects' > make: *** [all] Error 1 > > Interestingly trunk works fine but not the release_31 branch. > > Regards, > ismail >

Sebastian, > I just saw that the git branch remotes/origin/release_31 has been created > for llvm.  Unfortunately it is missing the right context: right now I can only > see 11 patches in that branch with the last patch having no parent. > > Could somebody please fix this? This looks like git-svn bug. If anyone knows "the cure" I'd be happy...

Hi Sebastian. > Anton, could you please try to fix the release_31 git branch? Sorry for late response - I was afk. Given that I received no complains about clang.git I will switch llvm.git soon :) -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

Hello Everyone As some of you already noticed release_31 branch on llvm.git was somehow created w/o history. I fixed this via manual grafting (kudos to John Wiegley!), but please carefully watch the results: 1. refs in release_31 branch should be changed. This is expected and this is the price we're paying for connected history (if you have something...

Won't it be http://llvm.org/svn/llvm-project/llvm/tags/RELEASE_31/final/ On Tue, Jan 8, 2013 at 7:46 PM, Pankaj Gode <godepankaj at yahoo.com> wrote: > Hi All, > > I was checking for GIT or SVN versions corresponding to llvm3.1 release by > checking svn and git logs, but failed to find the exact match. > > I checked with r156747, whic...

...ate] release_26 -> llvm.org/release_26 = [up to date] release_27 -> llvm.org/release_27 = [up to date] release_28 -> llvm.org/release_28 = [up to date] release_29 -> llvm.org/release_29 = [up to date] release_30 -> llvm.org/release_30 = [up to date] release_31 -> llvm.org/release_31 = [up to date] release_32 -> llvm.org/release_32 = [up to date] release_33 -> llvm.org/release_33 = [up to date] release_34 -> llvm.org/release_34 = [up to date] release_35 -> llvm.org/release_35 = [up to date] release_35 at 215010...

Hi all, We branched for the 3.1 release! (Yay!) If there are any fixes which you think should go into the release, please contact the code owners (http://llvm.org/docs/DeveloperPolicy.html#owners) so that they can approve the patches. No patches will be accepted into the 3.1 release without prior approval! This should be a great release! :-) -bw

I always though the /tags/RELEASE_xx/final branch would hold the final, released tarball contents, but this does not appear to be the case, at least not for 3.1. I can confirm that diffing /tags/RELEASE_31/final and the 3.1 tarball shows some non-trivial changes. The 3.2 release seems to be okay though; the diff only shows changes in the last-modified timestamps in the HTML docs. Though I just noticed that the source release has llvmbuild .pyc files. Won't including those cause issues? On Tu...

...; llvm.org/release_26 > = [up to date] release_27 -> llvm.org/release_27 > = [up to date] release_28 -> llvm.org/release_28 > = [up to date] release_29 -> llvm.org/release_29 > = [up to date] release_30 -> llvm.org/release_30 > = [up to date] release_31 -> llvm.org/release_31 > = [up to date] release_32 -> llvm.org/release_32 > = [up to date] release_33 -> llvm.org/release_33 > = [up to date] release_34 -> llvm.org/release_34 > = [up to date] release_35 -> llvm.org/release_35 > = [up to date]...

how to get this branch? still svn co http://llvm.org/svn/llvm-project/llvm/trunk llvm? Thank you. On Tue, Apr 17, 2012 at 2:16 PM, Bill Wendling <wendling at apple.com> wrote: > Hi all, > > We branched for the 3.1 release! (Yay!) > > If there are any fixes which you think should go into the release, please > contact the code owners

...ential null pointer dereference in EngineBuilder::selectTarget. The class has an optional pointer to the ErrorStr, which can be initialzied through setErrorStr() method. Although, it's strictly optional, selectTarget doesn't verify its value before assignment. Please find patch for branch release_31, revision 155051 attached. - Yury -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120509/c147de15/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: Targe...