llvm dev - Mar 2011 - [LLVMdev] [cfe-dev] Reminder: LLVM 2.9 Branching in One Week

Matthieu,

On Tue, Mar 1, 2011 at 8:02 AM, Matthieu Moy
<Matthieu.Moy at grenoble-inp.fr> wrote:
> At some point in the past, an anti-git-svn system had been set up on
> llvm.org. Has this been disabled since? I don't manage to do much with
> git-svn:
Maybe sure. Anton said it is disabled to access upper directories with svn.
Thus, we (accessing llvm.org remotely) cannot do git-svn with branches
for homebrew.

In contrast, I suppose Anton might create branches with git-svn.
Or I guess Andreas (aka earl) might know howto.
(I guess, Andreas might manipulate lowlevel git to create a branch initially)

Andreas and Anton, could you please launch git release branches for llvm.org?


...Takumi


ps. afaik llvm.org/git/llvm.git is diverged to
https://github.com/earl/llvm-mirror.

NAKAMURA Takumi <geek4civic at gmail.com> writes:
> Matthieu,
>
> On Tue, Mar 1, 2011 at 8:02 AM, Matthieu Moy
> <Matthieu.Moy at grenoble-inp.fr> wrote:
>> At some point in the past, an anti-git-svn system had been set up on
>> llvm.org. Has this been disabled since? I don't manage to do much
with
>> git-svn:
>
> Maybe sure. Anton said it is disabled to access upper directories with svn.
> Thus, we (accessing llvm.org remotely) cannot do git-svn with branches
> for homebrew.
This is exactly right.
> Andreas and Anton, could you please launch git release branches for
llvm.org?
I think the trouble with branches is the lockdown of the root repository
directory.  I tried something like this but it breaks due to the
restrictions:

git svn init --stdlayout https://<user>@llvm.org/svn/llvm-project/llvm \
 
--ignore-paths="^.*(Apple|PowerPC.*|SVA|eh-experimental|ggreif|non-call-eh|parallel|release_.*|vector_llvm|wendling|May2007|checker|cremebrulee|start|RELEASE_1.*|RELEASE_2[0-7])"

Obviously, replace <user> with whatever it needs to be to allow dcommit
to work.

Ideally we'd have clang and llvm-gcc git mirrors as well via the
--prefix argument to git-svn init, but let's not get ahead of ourselves.
:)

It appears that there's not much those of us who would like git branches
for svn release tags can do without help from the server side.

                            -Dave

Hi David
> I think the trouble with branches is the lockdown of the root repository
> directory.
Surely not (at the server)
> git svn init --stdlayout
https://<user>@llvm.org/svn/llvm-project/llvm \
>
 --ignore-paths="^.*(Apple|PowerPC.*|SVA|eh-experimental|ggreif|non-call-eh|parallel|release_.*|vector_llvm|wendling|May2007|checker|cremebrulee|start|RELEASE_1.*|RELEASE_2[0-7])"
Several problems here:
1. Bunch of additional branches / tags are created due to multiple
branch points. I don't recall for llvm, but for clang we'll end with
two tags per each release. Something like:
$ git branch -r
  trunk
  tags/RELEASE_26
  tags/RELEASE_26 at 84939
  tags/RELEASE_27
  tags/RELEASE_27 at 102415
  tags/RELEASE_28
  tags/RELEASE_28 at 115869

The problem will be much worse with new release branch scheme,
basically we'll need to add each branch by hand, etc...
2. We really don't want to push arbitrary branches to git repository.
It's really easy to add branch by an accident, so it will be much
better not to ignore stuff, but except - add by some pattern.
Unfortunately, git-svn does not allow this yet.

So, right now I'm experimenting with various ways of doing stuff, but
the results looks not pretty good.
If anything would give me a working all-in-one cmdline / .git/config
entry - I'd really appreciate this :)

-- 
With best regards, Anton Korobeynikov
Faculty of Mathematics and Mechanics, Saint Petersburg State University