-
-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move top-level .cpp files into their respective folders #1249
Conversation
@dialtr I still cannot add you to the reviewers list. This is probably because you are not in the list of collaborators. @akuker @rdmark Can you please add Tom to this list? I addition, I would appreciate the change of the SonarCloud setting I asked for in #1232 to be applied: Please disable this warning in SonarCloud:
We cannot address this issue because the bullseye compiler does not support "using enum", and whether/where to use "using enum" is optional anyway. |
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
Is this the right setting? I don't see anything with that exact wording: I've also added you as an owner for the SonarCloud project, so you should be able to make additional changes if needed. |
Invitation sent to @dialtr to become a collaborator. Let me know if you have any issues! |
Tony,
I got the invite and was able to confirm. Thanks!
TD
…On Mon, Oct 16, 2023 at 11:40 AM Tony Kuker ***@***.***> wrote:
Invitation sent to @dialtr <https://github.com/dialtr> to become a
collaborator. Let me know if you have any issues!
—
Reply to this email directly, view it on GitHub
<#1249 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB7G2LGYHZNTQ7UCKUI64VLX7VIPFAVCNFSM6AAAAAA6BYS6Z2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRUG43DIOBYGU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@akuker I think this is the right setting. Sometimes I am also struggling with the exact meaning/wording of the settings. Let's just give it a try, we will know soon whether it is correct. |
* Update Makefile, move top-level .cpp files * Move top-level .cpp files into their respective folders
* Update Makefile, move top-level .cpp files * Move top-level .cpp files into their respective folders
* Update Makefile, move top-level .cpp files * Move top-level .cpp files into their respective folders
No description provided.