Hi,
Just now I uploaded the new builds of MinGW-W64 based on GCC-4.9.0.
MinGW-W64 updated to rev.6604
Links:
32-bit:
posix-sjlj:
http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/4.9.0/threads-posix/sjlj/i686-4.9.0-release-pos
2014-04-30 20:05 GMT+02:00 JonY :
> Experimentals are outdated and unused and has not seen any
> changes for a long time, and unlikely to see any significant changes soon.
> The only gem left in experimental is ironcrate, which is still far from
> complete, I doubt there are actually active ironcra
On 4/30/2014 21:34, Rodny Spillig wrote:
>>
>> Because it was a pain to track down patches applied to other branches
>> and reapply it again and again, cherry-pick is god sent. Not to mention
>> merging is quick and simple. It is also far far easier to do a long term
>> private branch in git than i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 30.04.2014 18:41, LRN wrote:
> On 04.04.2014 2:21, JonY wrote:
>> On 4/4/2014 05:21, Erik van Pienbroek wrote:
>>>
>>> The following packages FAILED to rebuild:
>>>
>>> mingw-cairo-1.12.16-1 ** Package failed to build while it succeeded
>>> durin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04.04.2014 2:21, JonY wrote:
> On 4/4/2014 05:21, Erik van Pienbroek wrote:
>>
>> The following packages FAILED to rebuild:
>>
>> mingw-cairo-1.12.16-1 ** Package failed to build while it succeeded
>> during the previous mass rebuild ** Package ow
On Tue, Apr 29, 2014 at 6:00 AM, JonY wrote:
> On 4/29/2014 14:49, Rodny wrote:
>> JonY writes:
>>
>>>
>>> Hi,
>>>
>>> mingw-w64 may migrate from svn to git in the future, seeing that sf can
>>> now do multiple repos per project.
>>>
>>> Structure wise, everything under trunk will still stay to
On 4/30/2014 19:52, JonY wrote:
> On 4/30/2014 19:18, Ruben Van Boxem wrote:
>> 2014-04-30 12:45 GMT+02:00 JonY :
>>
>>> Hi,
>>>
>>> I have enabled read-only access to the git repos for testing purposes,
>>> the experimental directory is mostly outdated and can be left in SVN.
>>>
>>> Do try out th
On 4/30/2014 19:52, JonY wrote:
>> Another small nit: the branches still have tags, (v1.0 and v2.0), maybe get
>> rid of these for confusion's sake.
>>
>
Wait, I don't see them(???)
All I see is:
Branches
master
v1.x
v1.x@4408
v1.x@4409
v2.x
v2.x@4408
v2.x@4410
v3
On 4/30/2014 19:18, Ruben Van Boxem wrote:
> 2014-04-30 12:45 GMT+02:00 JonY :
>
>> Hi,
>>
>> I have enabled read-only access to the git repos for testing purposes,
>> the experimental directory is mostly outdated and can be left in SVN.
>>
>> Do try out the repos (git clone URL):
>>
>> mingw-w64
2014-04-30 12:45 GMT+02:00 JonY :
> Hi,
>
> I have enabled read-only access to the git repos for testing purposes,
> the experimental directory is mostly outdated and can be left in SVN.
>
> Do try out the repos (git clone URL):
>
> mingw-w64 proper - git://git.code.sf.net/p/mingw-w64/git
> webpag
Hi,
I have enabled read-only access to the git repos for testing purposes,
the experimental directory is mostly outdated and can be left in SVN.
Do try out the repos (git clone URL):
mingw-w64 proper - git://git.code.sf.net/p/mingw-w64/git
webpage - git://git.code.sf.net/p/mingw-w64/git-web
iron
11 matches
Mail list logo
