> As there's nothing we can do upstreams, I'm marking this as "not a bug" > and set the status to closed.
Why "nothing"? And it *is* a bug, IMO. My rebuttal is as the following: If the feature is implemented upstream it can get to CYGWIN, eventually. Not the other way around. Currently CYGWIN uses 8.15, which is not behind a lot. They catch up from time to time to right to the current versions of the tools... As for their response, here it is: > > > is unparsable in CYGWIN (scripting becomes problematic), because the > > > space is used both > > > in the group names (as obtained from Windows) and to delimit the group > > > names in the groups' > > > output: > > Such a proposal should be made to upstream coreutils, as it could > > possibly be of benefit to more platforms than just cygwin. Which is exactly what I was doing posting this suggestion here. Anton Lavrentiev Contractor NIH/NLM/NCBI
