Displaying 9 results from an estimated 9 matches for "release_24".
Did you mean:
release_26
2016 Feb 05
2
Why do we have a git tag called "release_35@215010"?
...ate] release_16 -> llvm.org/release_16
= [up to date] release_20 -> llvm.org/release_20
= [up to date] release_21 -> llvm.org/release_21
= [up to date] release_22 -> llvm.org/release_22
= [up to date] release_23 -> llvm.org/release_23
= [up to date] release_24 -> llvm.org/release_24
= [up to date] release_25 -> llvm.org/release_25
= [up to date] release_26 -> llvm.org/release_26
= [up to date] release_27 -> llvm.org/release_27
= [up to date] release_28 -> llvm.org/release_28
= [up to date] release_29 -> llv...
2011 Oct 06
0
[LLVMdev] svnsync of llvm tree
...runk in the SVN repos.
I think it contains branches of several previous releases:
$ git branch -r
llvm-upstream/master
llvm-upstream/release_1
llvm-upstream/release_16
llvm-upstream/release_20
llvm-upstream/release_21
llvm-upstream/release_22
llvm-upstream/release_23
llvm-upstream/release_24
llvm-upstream/release_25
llvm-upstream/release_26
llvm-upstream/release_27
llvm-upstream/release_28
llvm-upstream/release_29
llvm-upstream/svn-tags/RELEASE_1
llvm-upstream/svn-tags/RELEASE_20
llvm-upstream/svn-tags/RELEASE_21
llvm-upstream/svn-tags/RELEASE_22
llvm-upstream/svn-t...
2016 Feb 05
2
Why do we have a git tag called "release_35@215010"?
...; llvm.org/release_16
> = [up to date] release_20 -> llvm.org/release_20
> = [up to date] release_21 -> llvm.org/release_21
> = [up to date] release_22 -> llvm.org/release_22
> = [up to date] release_23 -> llvm.org/release_23
> = [up to date] release_24 -> llvm.org/release_24
> = [up to date] release_25 -> llvm.org/release_25
> = [up to date] release_26 -> llvm.org/release_26
> = [up to date] release_27 -> llvm.org/release_27
> = [up to date] release_28 -> llvm.org/release_28
> = [up to date]...
2011 Oct 06
1
[LLVMdev] svnsync of llvm tree
On 2011-08-29 04:21, Kurt Lidl wrote:
> While I agree bootstrapping a new mirror from scratch is time and
> resource consuming, this can be largely avoided by making a seed
> of the svn tree available. (Basically, I think that looks like
> a compressed tar file of the svn repository.) Or, a svnadmin dump
> of the repo could be made available for the adventurous.
Having the same
2008 Oct 07
0
[LLVMdev] 2.4 Branch Created
LLVMers,
The 2.4 branch has been created. On October 9th, I will be release pre-
release tar balls and binaries for testing.
If you want to check out the branch, you may do so with the following
commands:
svn co https://llvm.org/svn/llvm-project/llvm/branches/release_24
svn co https://llvm.org/svn/llvm-project/llvm-gcc-4.2/branches/release_24
svn co https://llvm.org/svn/llvm-project/test-suite/branches/release_24
Please do not commit directly to the branch. If you have a patch that
should be applied to the branch, you must get it approved by the
appropriate co...
2012 Apr 27
0
[LLVMdev] git branch release_31
...hes/*: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/*
--
With best regards,...
2012 Apr 26
2
[LLVMdev] git branch release_31
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
2011 Aug 29
2
[LLVMdev] svnsync of llvm tree
On Wed, Aug 17, 2011 at 01:47:02PM -0700, Benjamin Kramer wrote:
> On 17.08.2011, at 11:36, Kurt Lidl <lidl at pix.net> wrote:
>
> > Why can't I mirror the whole tree?
>
> The original reason for this limitation was that complete checkouts
> put a lot of stress on the server.
While I agree bootstrapping a new mirror from scratch is time and
resource consuming,
2011 Oct 06
0
[LLVMdev] MIPS 32bit code generation
...runk in the SVN repos.
I think it contains branches of several previous releases:
$ git branch -r
llvm-upstream/master
llvm-upstream/release_1
llvm-upstream/release_16
llvm-upstream/release_20
llvm-upstream/release_21
llvm-upstream/release_22
llvm-upstream/release_23
llvm-upstream/release_24
llvm-upstream/release_25
llvm-upstream/release_26
llvm-upstream/release_27
llvm-upstream/release_28
llvm-upstream/release_29
llvm-upstream/svn-tags/RELEASE_1
llvm-upstream/svn-tags/RELEASE_20
llvm-upstream/svn-tags/RELEASE_21
llvm-upstream/svn-tags/RELEASE_22
llvm-upstream/svn-t...