Hi,

It seems right to rebuild LDC not using master. However whilst there is a merge-2.065, it seems a long way behind merge-2.064 in terms of having everything from master merged in, along with there being lots of bug fixes in merge-2.064 not in merge-2.065.

I may have missed a memo, in which case apologies, but wouldn't it be better to effectively ditch merge-2.064 and put all effort into merge-2.065?

-- 
Russel. ============================================================================= Dr Russel Winder      t: +44 20 7585 2200   voip: sip:russel.winder@ekiga.net 41 Buckmaster Road    m: +44 7770 465 077   xmpp: russel@winder.org.uk London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder

Hi Russel!

On Thursday, 5 June 2014 at 05:38:48 UTC, Russel Winder via digitalmars-d-ldc wrote:
> Hi,
>
> It seems right to rebuild LDC not using master. However whilst there is
> a merge-2.065, it seems a long way behind merge-2.064 in terms of having
> everything from master merged in, along with there being lots of bug
> fixes in merge-2.064 not in merge-2.065.
>
> I may have missed a memo, in which case apologies, but wouldn't it be
> better to effectively ditch merge-2.064 and put all effort into
> merge-2.065?

I would recommend to use the merge-2.064 branch because all development happens in this branch. I'll merge this branch into master branch soon as you are the third person asking about the branches in two days...

The merge-2.065 branch misses some commits but should be usable, too. I do not ditch merge-2.064 in favor of merge-2.065 because the last remaining bug in merge-2.064 is also present in mere-2.065... I really want to push out the next stable release soon.

Regards,
Kai

On Thu, 2014-06-05 at 16:13 +0000, Kai Nacke via digitalmars-d-ldc
wrote:
[…]
> I would recommend to use the merge-2.064 branch because all development happens in this branch. I'll merge this branch into master branch soon as you are the third person asking about the branches in two days...
> 
> The merge-2.065 branch misses some commits but should be usable, too. I do not ditch merge-2.064 in favor of merge-2.065 because the last remaining bug in merge-2.064 is also present in mere-2.065... I really want to push out the next stable release soon.

Works for me :-)

Given I am using DMD 2.065, I had been thinking it would be better to use merge-2.065, but I'll try with merge-2.064 and hope I am not using any of the new features.

Thanks.

-- 
Russel. ============================================================================= Dr Russel Winder      t: +44 20 7585 2200   voip: sip:russel.winder@ekiga.net 41 Buckmaster Road    m: +44 7770 465 077   xmpp: russel@winder.org.uk London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder

On Thursday, 5 June 2014 at 17:42:44 UTC, Russel Winder via digitalmars-d-ldc wrote:
> On Thu, 2014-06-05 at 16:13 +0000, Kai Nacke via digitalmars-d-ldc
> wrote:
> […]
>> I would recommend to use the merge-2.064 branch because all development happens in this branch. I'll merge this branch into master branch soon as you are the third person asking about the branches in two days...
>> 
>> The merge-2.065 branch misses some commits but should be usable, too. I do not ditch merge-2.064 in favor of merge-2.065 because the last remaining bug in merge-2.064 is also present in mere-2.065... I really want to push out the next stable release soon.
>
> Works for me :-)
>
> Given I am using DMD 2.065, I had been thinking it would be better to
> use merge-2.065, but I'll try with merge-2.064 and hope I am not using
> any of the new features.
>
> Thanks.

I merged the latest changes from merge-2.064 into merge-2.065 branch a minute ago. Both branches are now up-to-date.

Regards,
Kai

On Fri, 2014-06-06 at 04:51 +0000, Kai Nacke via digitalmars-d-ldc
wrote:
[…]
> I merged the latest changes from merge-2.064 into merge-2.065 branch a minute ago. Both branches are now up-to-date.

Sponditious. I shall track merge-2.065 HEAD and report in any issues.

Thanks.

-- 
Russel. ============================================================================= Dr Russel Winder      t: +44 20 7585 2200   voip: sip:russel.winder@ekiga.net 41 Buckmaster Road    m: +44 7770 465 077   xmpp: russel@winder.org.uk London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder