Hi Pali!
On Thu, Nov 16, 2017 at 12:49 PM, wrote:
> Hi! And what are you going to do with all commits which you reverted in
> 4.043 version? As I remember, months ago you wrote that you reapply
> fixes, but nothing happened. Instead you started merging conflicting
> new pull requests which othe
On Friday 10 November 2017 10:13:55 Patrick M. Galbraith wrote:
> Greetings all!
>
> Michiel and I have been talking, weighing options of what course to take in
> dealing with moving forward-- with the goal of both offering both stability
> and the choice to have the latest functionality and bug f
And I would suggest to disable issue tracker on github as primary bug
tracker (according to DBD::mysql documentation) is on RT and also
probably all problems are reported there. The worst thing which can be
is to have two independent bug trackers, which is current situation.
Me too!
I look forward to getting pull requests reviewed and in the driver as
well as get your UTF-8 work in per my previous email. We can use all the
help we can get.
regards,
Patrick
On 11/11/17 3:53 AM, p...@cpan.org wrote:
On Friday 10 November 2017 10:13:55 Patrick M. Galbraith wrote:
om
-Original Message-
From: Darren Duncan [mailto:dar...@darrenduncan.net]
Sent: Friday, November 10, 2017 6:39 PM
To: dbi-users@perl.org
Subject: Re: DBD::mysql next steps
On 2017-11-10 5:58 PM, Dan Book wrote:
> On Fri, Nov 10, 2017 at 8:43 PM, Noel Butler wrote:
> G
On Friday 10 November 2017 10:13:55 Patrick M. Galbraith wrote:
> Greetings all!
>
> Michiel and I have been talking, weighing options of what course to take in
> dealing with moving forward-- with the goal of both offering both stability
> and the choice to have the latest functionality and bug f
On 2017-11-10 5:58 PM, Dan Book wrote:
On Fri, Nov 10, 2017 at 8:43 PM, Noel Butler wrote:
Given that things are only ever going to move forward with my/maria-sql
would it not be better to enable this by default, and have a "disable"
setting for those who want to run something of anti
On Fri, Nov 10, 2017 at 8:43 PM, Noel Butler wrote:
>
> Given that things are only ever going to move forward with my/maria-sql
> would it not be better to enable this by default, and have a "disable"
> setting for those who want to run something of antiques?
>
> Because in years to come there wil
On 11/11/2017 01:13, Patrick M. Galbraith wrote:
> Greetings all!
>
> Michiel and I have been talking, weighing options of what course to take in
> dealing with moving forward-- with the goal of both offering both stability
> and the choice to have the latest functionality and bug fixes as well a
I agree in principle with Patrick's plan.
My strong recommendation for continuing development under a different module
name was based on the assumption (but not the knowledge) that the Unicode/Blob
problems were rooted in the DBD::mysql codebase in such a way that they blocked
the ability to u
Greetings all!
Michiel and I have been talking, weighing options of what course to take in
dealing with moving forward-- with the goal of both offering both stability
and the choice to have the latest functionality and bug fixes as well as
give contributors the opportunity to be part of overall i
11 matches
Mail list logo
