similar to: [LLVMdev] llvm.git mirror & release_31 branch

> In your svn section of llvm/.git/config, you can specify how to map > the svn branches to different name spaces, something like this: > > [svn-remote "svn"] >        [...] >        branches = branches/*:refs/remotes/origin/* >        fetch = branches:refs/remotes/origin > > I would also change "branches = branches/*:refs/remotes/origin/*" > into

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

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 is actually removing an older > release_31 branch:

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 to apply it. -- With best

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 for rebranching. This

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

>> 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

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

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

Hi; This is on Linux/x86-64, I get this at stage1: make[2]: Entering directory `/home/abuild/rpmbuild/BUILD/llvm/stage1/projects/compiler_rt' Makefile:6: make/config.mk: No such file or directory Makefile:7: make/util.mk: No such file or directory Makefile:16: *** Refusing to build with empty ProjObjRoot variable. Stop. make[2]: Leaving directory

ping? Still fails on 3.1 branch. On Tue, Apr 17, 2012 at 5:35 PM, İsmail Dönmez <ismail at namtrac.org> wrote: > > Hi; > > This is on  Linux/x86-64, I get this at stage1: > > make[2]: Entering directory `/home/abuild/rpmbuild/BUILD/llvm/stage1/projects/compiler_rt' > Makefile:6: make/config.mk: No such file or directory > Makefile:7: make/util.mk: No such file or

This has been discussed many times. Might want to take a look in the mailing list archives. :) cmake and autotools are on roughly equal footing at this point with chandler and I handling each of them respectively and fairly quickly. git vs. svn is a different story though. -eric On Thu, Nov 15, 2012 at 8:31 AM, Greg Fitzgerald <garious at gmail.com> wrote: > Hi, > > Has there

> cmake and autotools are on roughly equal footing at this point with chandler > and I handling each of them respectively and fairly quickly. git vs. svn is > a different story though. Would you be willing to put this commitment to autotools in CODE_OWNERS.TXT? Sometimes I have needed to make changes to Makefiles and didn't know who was the right person to CC for it, so having an

Hi, Has there been discussion about having svn mirror git instead of vice versa? I've been happy with the git+cmake+ninja combo for a while now, but the online docs suggests this configuration is second-class to svn+autotools+make. Is the community transitioning to any particular configuration? Thanks, Greg On Wed, Nov 14, 2012 at 9:19 AM, Anton Korobeynikov <anton at

Should be there On Fri, Nov 16, 2012 at 3:00 PM, NAKAMURA Takumi <geek4civic at gmail.com> wrote: > Anton, please add release_32 also in; > > clang-tools-extra > compiler-rt > dragonegg > libcxxabi > lldb > > They have release_32 in svn. I don't know they might be released, though. > > And, could you suppress generating refs/heads/svn-tags and prune them

Anton, please add release_32 also in; clang-tools-extra compiler-rt dragonegg libcxxabi lldb They have release_32 in svn. I don't know they might be released, though. And, could you suppress generating refs/heads/svn-tags and prune them for now? I am sure that orphan branches will stress the llvm.org server to begin git-pack-ing whole tree. ...Takumi 2012/11/15 Anton Korobeynikov

Should be there. Please let me know if there are any problems with them On Wed, Nov 14, 2012 at 9:19 PM, Anton Korobeynikov <anton at korobeynikov.info> wrote: >> I can't find any release_32 branch at http://llvm.org/git/llvm.git or http://llvm.org/git/clang.git. > Unfortunately, this requires manual grafting, since git-svn does > really bad job here. > > I'm going

> I can't find any release_32 branch at http://llvm.org/git/llvm.git or http://llvm.org/git/clang.git. Unfortunately, this requires manual grafting, since git-svn does really bad job here. I'm going to work on this tonight. -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

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

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, which is the last version it shows