[Phpmyadmin-devel] about reports.phpmyadmin.net
Hi, I would like to know if my workflow is correct. I had a look at [0] which pointed me to [1] (private link). In this collection of reports, I don't see this incident for phpMyAdmin 4.1.9 and more recent (the 4.2.0-dev reference is probably at an early stage of 4.2.0). We got 25 incidents for this one in version 4.1.8. Can I deduce that this bug has been indirectly fixed, starting with 4.1.9? [0] https://sourceforge.net/p/phpmyadmin/bugs/4329/ [1] https://reports.phpmyadmin.net/reports/view/1572 -- Marc Delisle
On 4/22/14, Marc Delisle <marc@infomarc.info> wrote:
Hi,
I would like to know if my workflow is correct. I had a look at [0] which pointed me to [1] (private link). In this collection of reports, I don't see this incident for phpMyAdmin 4.1.9 and more recent (the 4.2.0-dev reference is probably at an early stage of 4.2.0).
We got 25 incidents for this one in version 4.1.8.
Can I deduce that this bug has been indirectly fixed, starting with 4.1.9?
Hi Marc, 'mysql_doc_template is not defined' is not fixed.. I couldn't reproduce the scenario when it happens so couldn't fix.. User reports didn't help much to sort out the scenario.. Regards -- Atul Pratap Singh http://blog.atulsisodia.in/
On 4/22/14, Atul Pratap Singh <atulpratapsingh05@gmail.com> wrote:
On 4/22/14, Marc Delisle <marc@infomarc.info> wrote:
Hi,
I would like to know if my workflow is correct. I had a look at [0] which pointed me to [1] (private link). In this collection of reports, I don't see this incident for phpMyAdmin 4.1.9 and more recent (the 4.2.0-dev reference is probably at an early stage of 4.2.0).
We got 25 incidents for this one in version 4.1.8.
Can I deduce that this bug has been indirectly fixed, starting with 4.1.9? Also, I can't say surely about it getting indirectly fixed.
-- Atul Pratap Singh http://blog.atulsisodia.in/
Atul Pratap Singh a écrit :
On 4/22/14, Atul Pratap Singh <atulpratapsingh05@gmail.com> wrote:
On 4/22/14, Marc Delisle <marc@infomarc.info> wrote:
Hi,
I would like to know if my workflow is correct. I had a look at [0] which pointed me to [1] (private link). In this collection of reports, I don't see this incident for phpMyAdmin 4.1.9 and more recent (the 4.2.0-dev reference is probably at an early stage of 4.2.0).
We got 25 incidents for this one in version 4.1.8.
Can I deduce that this bug has been indirectly fixed, starting with 4.1.9? Also, I can't say surely about it getting indirectly fixed.
But isn't the absence of reports for > 4.1.8 a good indication? -- Marc Delisle
participants (2)
-
Atul Pratap Singh -
Marc Delisle