Displaying 3 results from an estimated 3 matches for "r258223".
Did you mean:
28223
2016 Jan 19
8
[3.8 Release] RC1 has been tagged
...ng non-legacy llvm-dev this time; apologies if you get this
twice. Please don't reply-all to the first one.)
On Tue, Jan 19, 2016 at 3:47 PM, Hans Wennborg <hans at chromium.org> wrote:
> Dear testers,
>
> Start your engines; 3.8.0-rc1 was just tagged from the 3.8 branch at
> r258223. (It took a little longer than I'd planned, sorry about that.)
>
> There are still a bunch of open merge requests and bug reports, but I
> wanted to get the tag in so we can see what the build and test status
> are on the various platforms.
>
> I verified that it currently bui...
2016 Jan 22
3
[cfe-dev] [3.8 Release] RC1 has been tagged
...t;> twice. Please don't reply-all to the first one.)
>>
>> On Tue, Jan 19, 2016 at 3:47 PM, Hans Wennborg <hans at chromium.org> wrote:
>> > Dear testers,
>> >
>> > Start your engines; 3.8.0-rc1 was just tagged from the 3.8 branch at
>> > r258223. (It took a little longer than I'd planned, sorry about that.)
>> >
>> > There are still a bunch of open merge requests and bug reports, but I
>> > wanted to get the tag in so we can see what the build and test status
>> > are on the various platforms.
>&g...
2016 Jan 20
2
[3.8 Release] RC1 has been tagged
...twice. Please don't reply-all to the first one.)
>>
>> On Tue, Jan 19, 2016 at 3:47 PM, Hans Wennborg <hans at chromium.org>
>> wrote:
>>> Dear testers,
>>>
>>> Start your engines; 3.8.0-rc1 was just tagged from the 3.8 branch at
>>> r258223. (It took a little longer than I'd planned, sorry about that.)
>>>
>>> There are still a bunch of open merge requests and bug reports, but I
>>> wanted to get the tag in so we can see what the build and test status
>>> are on the various platforms.
>>&...