search for: r155051

...   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 'release_31'. The diff with this version though gives me marginally less differences. Which SVN or GIT version should be considered as equivalent to llvm3.1 release ? Thanks & Regards, Pankaj -------------- next part -------------- An HTML a...

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 "old release_31 branch" was created...

...oject/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 'release_31'. The > diff with this version though gives me marginally less differences. > > Which SVN or GIT version should be considered as equivalent to llvm3.1 > release ? > > Thanks & Regards, > Pankaj > > > __...

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: > > 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. > &gt...

...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 'release_31'. The >> diff with this version though gives me marginally less differences. >> >> Which SVN or GIT version should be considered as equivalent to llvm3.1 >> release ? >> >> Thanks & Regards, >&...

> 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

...ld you please try to fix the release_31 git branch? Thanks, Sebastian > 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: >> >> Revision 155050 >> Author:         void >> Date:   Wed Apr 18 16:38:33 2012 CDT (11 days, 20 hours ago) >> Log Message:    Removing old release_31 bran...

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