Displaying 10 results from an estimated 10 matches for "rebranching".
Did you mean:
branching
2012 Apr 30
2
[LLVMdev] git branch release_31
...ee
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 on r154899:
Revision 154899
Author: void
Date: Mon Apr 16 21:00:08 2012 CDT (13 days, 16 hours ago)
Log Message: Creating release_31 branch
Here is how I fixed this in my local git repo: looking at the last
commit to trunk r155049, before t...
2012 May 06
0
[LLVMdev] git branch release_31
...en 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 on r154899:
>
> Revision 154899
> Author: void
> Date: Mon Apr 16 21:00:08 2012 CDT (13 days, 16 hours ago)
> Log Message: Creating release_31 branch
>
>
> Here is how I fixed this in my local git rep...
2012 Apr 27
0
[LLVMdev] git branch release_31
> 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
2012 May 07
2
[LLVMdev] git branch release_31
...gt;> 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 on r154899:
>>
>> Revision 154899
>> Author: void
>> Date: Mon Apr 16 21:00:08 2012 CDT (13 days, 16 hours ago)
>> Log Message: Creating release_31 branch
>>
>>
>> Here...
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
2009 Feb 20
0
[LLVMdev] libLTO warning
...e!
>
> I haven't noticed any ill-effects. Is this a harmless warning or does it
> need to be fixed?
>
> I'm on Linux/Fedora 9, x86-64.
The warnings are harmless, but regardless libLTO shouldn't be trying to
build on any platform except Darwin.
It looks like the 2.5 rebranching took place at just the wrong time and
picked up a change when I tried to have libLTO build on Linux as well.
That change should never have made it into the 2.5 branch.
Tanya, could you please revert 62987 from the 2.5 branch? It's this patch:
http://llvm.org/viewvc/llvm-project/llvm/branches...
2007 Feb 24
1
Branches (again)
A long long time ago, I asked about the different tinc branches.
Guus, you said at the time that
* trunk is 1.0, bugfixes only
* 1.0-gnutls, POKEY, and pre4-cube are stagnant
* 2.0 is where new work should happen...at the time, it didn't
compile, and it appears it still doesn't
This answer discouraged me; I have trouble getting excited about new
work in a branch that's been
2009 Feb 20
2
[LLVMdev] libLTO warning
Hi all,
I just svn-updated the 2.5 branch on my machine and I noticed this warning
during the build.
*** Warning: Linking the shared library
/home/maurice/installation/llvm/Debug/lib/libLTO.la against the non-libtool
*** objects /home/maurice/installation/llvm/Debug/lib/LLVMCppBackend.o
/home/maurice/installation/llvm/Debug/lib/LLVMMSIL.o
/home/maurice/installation/llvm/Debug/lib/LLVMCBackend.o
2016 Jan 08
2
Diff to add ARMv6L to Target parser
Thanks for the clarifications, Bob!
I’ve spent some time with the head of the llvm.org repo, and I now understand a lot better what Renato and Tim were talking about re. the architecture aliases. The patch to add v6l, therefore, seems simple enough. I haven’t been able to test it in my usual flow, because that involves the whole swift stack. I’m considering creating a program that links to
2016 Jan 05
6
Diff to add ARMv6L to Target parser
> You assume triples make sense. That's the first mistake everyone does
> when thinking about triples. :)
I know they don't make sense in many corner cases, but I think
discarding logic where it *does* exist is a mistake.
> AFAIK, "ARMv7B" is only used by HighBank, which is no more. But that,
> too, was "ARMv7A big endian".
I believe it's what any