aboutsummaryrefslogtreecommitdiff
path: root/lldb/source/Commands/CommandObjectSource.cpp
diff options
context:
space:
mode:
authorBalazs Benics <benicsbalazs@gmail.com>2024-11-13 09:50:09 +0100
committerGitHub <noreply@github.com>2024-11-13 09:50:09 +0100
commit12dcaa2e1e6c46d8a1b440d8a836d6b81ab92efb (patch)
tree1284e78db0c4867d6821fe11c5f217ea468a1a76 /lldb/source/Commands/CommandObjectSource.cpp
parent6ff41e860fdb69bb9e234e003255aae9accff79a (diff)
downloadllvm-12dcaa2e1e6c46d8a1b440d8a836d6b81ab92efb.zip
llvm-12dcaa2e1e6c46d8a1b440d8a836d6b81ab92efb.tar.gz
llvm-12dcaa2e1e6c46d8a1b440d8a836d6b81ab92efb.tar.bz2
[clang] Add steakhal to the Clang Static Analyzer maintainers (#114991)
I've been contributing to the Clang Static Analyzer for a while now. I think from 2019, or something like that. I've ensured the quality of the Static Analyzer releases for the last ~4-6 releases now, with testing, fixing and backporting patches; also writing comprehensive release notes for each release. I have a strong sense of ownership of the code I contribute. I follow the issue tracker, and also try to follow and participate in RFCs on Discourse if I'm not overloaded. I also check Discord time-to-time, but I rarely see anything there. You can find the maintainer section of the LLVM DeveloperPolicy [here](https://llvm.org/docs/DeveloperPolicy.html#maintainers) to read more about the responsibilities.
Diffstat (limited to 'lldb/source/Commands/CommandObjectSource.cpp')
0 files changed, 0 insertions, 0 deletions