similar to: [LLVMdev] git branch release_31

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

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

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:

> 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

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

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 on top you might want to do git pull

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

> On 2016-Feb-05, at 15:22, James Y Knight <jyknight at google.com> wrote: > > That usually happens when someone deletes and then recreates an svn branch with the same name, as happened in r215001 and r215011. > It can be deleted now, if anyone wants to. ``` $ git push llvm.org :release_35 at 215010 fatal: unable to access 'http://llvm.org/git/llvm.git/': The requested

I've been using Jakob's commands below, but it has stopped working for me. This happened roughly around the time when Anton added the other branches, but I'm not sure if that was the cause or not. The symptom is that the "git svn rebase -l" command does nothing except say that the master branch is already up to date, and "git svn dcommit" complains that files are

Hi Martin, On Fri, 3 Aug 2018 at 14:10, Martin J. O'Riordan <MartinO at theheart.ie> wrote: > $ git branch --list > * master > martino By default "git branch" only lists local branches. "git branch -a" will list all of them, including (for me) "remotes/origin/release_70". If you just type "git checkout release_70" git will

On Feb 1, 2011, at 12:20 PM, Anton Korobeynikov wrote: > Hello Everyone, > > It seems given the decent amount of discussions it's time to make > small announcement. > > So, official git mirrors are available for some subset of LLVM > projects. They were used by some LLVM developers for couple of months > already and seem to be stable enough. Thank you for setting

On Mar 21, 2011, at 1:47 PM, Bob Wilson wrote: > I've been using Jakob's commands below, but it has stopped working for me. This happened roughly around the time when Anton added the other branches, but I'm not sure if that was the cause or not. The symptom is that the "git svn rebase -l" command does nothing except say that the master branch is already up to date, and

Hello Everyone, It seems given the decent amount of discussions it's time to make small announcement. So, official git mirrors are available for some subset of LLVM projects. They were used by some LLVM developers for couple of months already and seem to be stable enough. Right now there is a mirroring for LLVM itself and clang. More can be added per requests. The mirrors are made via

Hello Justin, > What am I missing here?  Should the new layout affect the git workflow? No. Stuff was just added. Trunk is still available as "master" as before. -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

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

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