Re: Is this the kind of "bug" you welcome reporting on one of your Standards (Shell Command Language)

2022-01-13 Thread Mark Galeck via austin-group-l at The Open Group
austingroupbugs.net ... if it is (a), then the > maintainers of those shells are generally on this list too, and will take the > appropriate action. > -- > Nick > > On Wed, Jan 12, 2022 at 7:01 AM Mark Galeck via austin-group-l at The Open > Group wrote: >> &

Re: Is this the kind of "bug" you welcome reporting on one of your Standards (Shell Command Language)

2022-01-13 Thread Mark Galeck via austin-group-l at The Open Group
the draft, to an email to the customer that raised the issue, with an explanation that this is what the intent is . I would rather not point to or provide the whole draft, for fear of confusion. Is that OK for me to do that? On Thu, Jan 13, 2022 at 3:36 AM Geoff Clare via austin-group-l at The Open

Is this the kind of "bug" you welcome reporting on one of your Standards (Shell Command Language)

2022-01-12 Thread Mark Galeck via austin-group-l at The Open Group
Hello, a few years ago, I used to report a number of "bugs" on www.austingroupbugs.net , however, my reporting was not acted upon, which may be because I did not properly understand what you care about or not. So before I do that again, since I don't want to waste anybody's time, I want to ask

Re: Is this the kind of "bug" you welcome reporting on one of your Standards (Shell Command Language)

2022-01-14 Thread Mark Galeck via austin-group-l at The Open Group
fect reports applied. > > I hope this helps. > regards > Andrew > > > On 13 Jan 2022, at 13:02, Mark Galeck via austin-group-l at The Open Group > > wrote: > > > > Yes thank you, this is very helpful. > > > > Right now, I point the customers to