Mark,
On 11/21/17 7:58 AM, Mark Thomas wrote:
> All,
>
> I've been looking at jk/trunk with a view to rolling a release in the
> near future. (It has been just over a year since the last release.)
>
> As I have been looking through the source, I have noticed a number of
> components that we stil
On 21/11/17 14:50, Rémy Maucherat wrote:
> On Tue, Nov 21, 2017 at 1:58 PM, Mark Thomas wrote:
>
>> All,
>>
>> I've been looking at jk/trunk with a view to rolling a release in the
>> near future. (It has been just over a year since the last release.)
>>
>> As I have been looking through the sour
On Tue, Nov 21, 2017 at 1:58 PM, Mark Thomas wrote:
> All,
>
> I've been looking at jk/trunk with a view to rolling a release in the
> near future. (It has been just over a year since the last release.)
>
> As I have been looking through the source, I have noticed a number of
> components that we
Am 21.11.2017 um 13:58 schrieb Mark Thomas:
All,
I've been looking at jk/trunk with a view to rolling a release in the
near future. (It has been just over a year since the last release.)
As I have been looking through the source, I have noticed a number of
components that we still include in th
All,
I've been looking at jk/trunk with a view to rolling a release in the
near future. (It has been just over a year since the last release.)
As I have been looking through the source, I have noticed a number of
components that we still include in the source that I think we
can/should remove bef
