> Frankly, I don't believe that you're still wasting our time arguing > about this completely trivial matter.
Trivial or complex, once we published our spec we must scrutinize each and every subsequent change request. Your 496592 bug report was filed on 12/25/01 and we responded on 1/11/02 that we were going to defer it past v1.1.0 so that we would have more time to investigate. We did not have enough information nor the resources to resolve this particular problem in time for v1.1.0. https://sourceforge.net/tracker/index.php?func=detail&aid=496592&group_id=1107&atid=101107 The gLSB v1.1.1 is not going to happen this week or next, and we have other pressing issues which have higher priority. One of those priorities is the LSB Certification Policies (or terms & conditions, and processes). Here is how bin=1 will be resolved. The Written Spec bug 496592 will be reviewed by the pending Specification Authority (SA). If accepted, then the SA will make changes to the gLSB v1.1.0 errata, the future gLSB v1.1.1, and the test suites. The only thing that speeds up the process is sufficient information and a willingness to participate in the resolution procedure. George (gk4)
