Refreshed build of SM 2.42.9ESR

classic Classic list List threaded Threaded
25 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Re: Refreshed build of SM 2.42.9ESR

Frank-Rainer Grahl-3
When you do 2.49.1 for OS/2 make sure to use the mozilla patches in the
THUNDERBIRD_52_VERBRANCH. Most are for OSX but there are a few critical ones
for mailnews in it.

FRG

Dave Yeo wrote:

> Steve Wendt wrote:
>> On 10/14/2017 09:17 PM, Dave Yeo wrote:
>>
>>> Hopefully the move to 52ESR will fix some of these issues, I
>>> understand the SM release is solid.
>>
>> But so far unreleased; perhaps the OS/2 version won't be several months
>> behind other platforms for once.  :)
>
> You're right, I was getting confused with 2.48. It would be nice to be not a
> year behind. It makes it hard just looking stuff up. I miss the days when
> trunk would usually build :)
> Dave
_______________________________________________
dev-ports-os2 mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-ports-os2
Reply | Threaded
Open this post in threaded view
|

Re: Refreshed build of SM 2.42.9ESR

Steve Wendt
In reply to this post by Steve Wendt
On 10/15/2017 12:41 PM, Steve Wendt wrote:

>> Hopefully the move to 52ESR will fix some of these issues, I
>> understand the SM release is solid.
>
> But so far unreleased; perhaps the OS/2 version won't be several
> months behind other platforms for once.  :)

The counter has started.  :-p
_______________________________________________
dev-ports-os2 mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-ports-os2
Reply | Threaded
Open this post in threaded view
|

Re: Refreshed build of SM 2.42.9ESR

Dave Yeo-3
In reply to this post by Frank-Rainer Grahl-3
Frank-Rainer Grahl wrote:
> When you do 2.49.1 for OS/2 make sure to use the mozilla patches in the
> THUNDERBIRD_52_VERBRANCH. Most are for OSX but there are a few critical
> ones for mailnews in it.
>

Thanks for the heads up.
How does the workflow usually work with HG? I'm now used to the way Git
handles branches and looking at your branch, it doesn't seem to contain
the various fixes applied to head.
Unluckily Bitwise chose to go with Git for their fork so I have to
figure out how to merge the THUNDERBIRD_52_VERBRANCH into their tree.
Dave
_______________________________________________
dev-ports-os2 mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-ports-os2
Reply | Threaded
Open this post in threaded view
|

Re: Refreshed build of SM 2.42.9ESR

Frank-Rainer Grahl-3
The default branch was merged in changeset 5fb6af232f11 on 10/02 to the
Thunderbird branch. This was the Firefox 52.4 release. Later changes in the
mozilla branch will only be picked up in the next release.

I could send you a comnined patch from my local copy but it also contains
backported VS2017 fixes which might clash with the OS/2 makefiles.

FRG

Dave Yeo wrote:

> Frank-Rainer Grahl wrote:
>> When you do 2.49.1 for OS/2 make sure to use the mozilla patches in the
>> THUNDERBIRD_52_VERBRANCH. Most are for OSX but there are a few critical
>> ones for mailnews in it.
>>
>
> Thanks for the heads up.
> How does the workflow usually work with HG? I'm now used to the way Git
> handles branches and looking at your branch, it doesn't seem to contain the
> various fixes applied to head.
> Unluckily Bitwise chose to go with Git for their fork so I have to figure out
> how to merge the THUNDERBIRD_52_VERBRANCH into their tree.
> Dave
_______________________________________________
dev-ports-os2 mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-ports-os2
Reply | Threaded
Open this post in threaded view
|

Re: Refreshed build of SM 2.42.9ESR

Frank-Rainer Grahl-3
In reply to this post by Dave Yeo-3
Dave I extracted the patches from a clean branch and sent you an email with them.

FRG

Dave Yeo wrote:

> Frank-Rainer Grahl wrote:
>> When you do 2.49.1 for OS/2 make sure to use the mozilla patches in the
>> THUNDERBIRD_52_VERBRANCH. Most are for OSX but there are a few critical
>> ones for mailnews in it.
>>
>
> Thanks for the heads up.
> How does the workflow usually work with HG? I'm now used to the way Git
> handles branches and looking at your branch, it doesn't seem to contain the
> various fixes applied to head.
> Unluckily Bitwise chose to go with Git for their fork so I have to figure out
> how to merge the THUNDERBIRD_52_VERBRANCH into their tree.
> Dave
_______________________________________________
dev-ports-os2 mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-ports-os2
12