Re: [ntp:questions] Time to fix reported driver bug.
On Mon, Mar 17, 2014 at 12:01 AM, Danny Mayer ma...@ntp.org wrote: A patch WAS submitted for this though it was done inline instead of as an attachment I added a patch against p433 as an attachment. I recommend that you mark it as possibly blocking 4.2.8 How to do that isn't immediately obvious and I'm not sure I want to learn how to use Bugzilla. Your explanation in the report seems to be adequate but someone needs to examine the code to see if the fix has any side effects, especially for other devices. I added a comment. ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
[ntp:questions] Time to fix reported driver bug.
I reported a bug in a driver about a month ago. Should I expect a feedback other than having it assigned to the refclock maintainers? Are times to fix on the scale of months or years? ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] Time to fix reported driver bug.
On 15/03/14 18:36, Paul wrote: I reported a bug in a driver about a month ago. Should I expect a feedback other than having it assigned to the refclock maintainers? Are times to fix on the scale of months or years? Assuming you are talking about the reference implementation of ntpd, it is going to depend on which driver, and the nature of the fault. If it is for a driver for a piece of hardware that is not available to an active developer, and the bug is not trivially obvious, and easy to fix, it could take forever. In my experience, in the commercial world, one month would only be achieved if the bug was business critical. If you tell us which bug report, someone may be able to indicate whether there is a competent developer, and how important it is. ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] Time to fix reported driver bug.
On Sun, Mar 16, 2014 at 9:53 AM, David Woolley david@ex.djwhome.demon.invalid wrote: If you tell us which bug report, someone may be able to indicate whether there is a competent developer, and how important it is. 2557. In most cases (~100%) it's inconsequential. I only noticed when adding another device in the Trimble family but if there's active support I'd submit a patch for it. ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] Time to fix reported driver bug.
On 2014-03-15, Paul tik-...@bodosom.net wrote: I reported a bug in a driver about a month ago. Should I expect a feedback other than having it assigned to the refclock maintainers? Are times to fix on the scale of months or years? Perhaps if you also reminded us all of what the bug was, it would also help. for example, that bug could be because of a configuration error which would be fixable very very quickly. ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] Time to fix reported driver bug.
On 2014-03-16, Paul tik-...@bodosom.net wrote: On Sun, Mar 16, 2014 at 9:53 AM, David Woolley david@ex.djwhome.demon.invalid wrote: If you tell us which bug report, someone may be able to indicate whether there is a competent developer, and how important it is. 2557. In most cases (~100%) it's inconsequential. I only noticed when adding another device in the Trimble family but if there's active support I'd submit a patch for it. Why would you not submit a patch for it if you have one? Remember that ntpd is maintained by volunteers. (How much did you pay to download and install ntpd?) And if it is a real corner case bug, why would a volunteer instantly jump on it, when the complainer does not even offer any help? ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] Time to fix reported driver bug.
On Sun, Mar 16, 2014 at 2:22 PM, William Unruh un...@invalid.ca wrote: I only noticed when adding another device in the Trimble family but if there's active support I'd submit a patch for it. Why would you not submit a patch for it if you have one? I meant submit a patch for the new device. I supplied a patch for bug 2557 in the report. ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
Re: [ntp:questions] Time to fix reported driver bug.
On 3/16/2014 4:11 PM, Paul wrote: On Sun, Mar 16, 2014 at 2:22 PM, William Unruh un...@invalid.ca wrote: I only noticed when adding another device in the Trimble family but if there's active support I'd submit a patch for it. Why would you not submit a patch for it if you have one? I meant submit a patch for the new device. I supplied a patch for bug 2557 in the report. A patch WAS submitted for this though it was done inline instead of as an attachment. I recommend that you mark it as possibly blocking 4.2.8 so that it gets some attention. Your explanation in the report seems to be adequate but someone needs to examine the code to see if the fix has any side effects, especially for other devices. Danny ___ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
