git branch release_31

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

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.

Hi Anton,

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.

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 something like "branches = branches/*:refs/remotes/branches/*"

Thanks,
Sebastian

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 something like "branches = branches/*: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/*

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

FYI, I have been maintaining my own release_31 manually on github.com/chapuni.

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

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

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

llvm.git should be sane

Thanks Anton. The release_31 branch looks good now in the git repo.

Sebastian