On Apr 12, 2013, at 7:19 AM, William Siegrist <wsiegrist@apple.com> wrote:

Sorry for the delay. We are working on the release and hope to have it out soon.

Just had a "Doh!" moment. Does it help when filing bug reports to review the source code to see if we can pin down the underlying cause of the problem (and optionally test a fix)? That is, is the bug more likely to get fixed a little faster doing this? I filed a bug report that probably affects very few people (the user's launchd process isn't generating BSM audit records properly; I suspect it isn't setting its audit mask correctly), and I hadn't thought of looking through the source code before filing a bug report. Should I do this in the future? Thanks, Todd _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.app... This email sent to site_archiver@lists.apple.com