strftime has wrong documentation (copy-and-paste?)

[bostick]

I filed:
https://issuetracker.google.com/issues/412707575

2 months ago, but there hasn't been any activity. I'm wondering if this is the correct place to file this issue?

[enh-google]

as you're about to see as soon as i finish typing, yes, github is a better place to file bugs because it's directly maintained by the folks who work on the ndk ... whereas google's own bug tracker is a weird place where public bugs are concerned. theoretically that bug should have been assigned to me (i just clicked "assign to default" to check that some configuration hadn't been lost, and that worked!) but for some reason it wasn't.

i thought we'd changed the text over there to say "prefer github", but another problem over there is that there are too many similar-but-different places to file, and -- because we don't own the configuration in the same way we do the github configuration -- things do have a habit of changing under our feet :-(

[enh-google]

ah, i see what happened --- you filed under frameworks because you were misled by the term "API documentation bugs" on https://github.com/android/ndk/issues. (that's just for Android API, not C/POSIX stuff.)

and then when someone moved the bug to the correct component, they forgot that you have to manually click "assign to default" because why would the computer do that for you? /s

reopening because @DanAlbert should probably clarify the bug template.

[DanAlbert]

No, it's fine for that to be filed in buganizer, it just should have been triaged to libc and not to an unmonitored bug component that I keep closing (so that this doesn't happen) but keeps being reopened.

If you want bionic doc bugs filed here rather than in buganizer that's fine, but most people are not going to get it right no matter how I try to clarify the wording in the "file a bug" landing page. A lot of people don't know the difference between a libc API and an Android API (and we have extensions to POSIX and C, especially in the linker, where there is no clear line).

[enh-google]

yeah, it would be good to be clear that "bionic bugs definitely shouldn't go to the frameworks component" (given that it's basically a black hole), but i've had one too many "how do i create a socket on android?" type questions to think people understand what we mean by "android api".

still, explicitly saying something like "ISO C, POSIX, or a BSD/GNU extension" might help for those who do know the difference?