Skip to content
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

Apply config.c refactorings #148

Merged
merged 3 commits into from
Jul 11, 2024
Merged

Apply config.c refactorings #148

merged 3 commits into from
Jul 11, 2024

Conversation

clumens
Copy link

@clumens clumens commented Jul 1, 2024

Continuing with #82, this is the next couple patches that address the use of global variables in config.[ch]. I made a couple changes to the original patches - get rid of _ptr from the variable names, add braces around conditional blocks in code that this touches, and removing a function instead of marking it as unused.

I tested this only briefly, by installing updated packages and making sure that booth started and could grant tickets.

Note - this builds on top of #147 so that needs to be merged first, then I'll rebase this one and it can be merged as well.

@clumens clumens requested a review from jfriesse July 1, 2024 18:24
@clumens
Copy link
Author

clumens commented Jul 5, 2024

Rebased on top of just merged mock patches.

@jfriesse
Copy link
Member

jfriesse commented Jul 10, 2024

I've checked commits twice and it looks there is no obvious problem codewise, but because you are native English speaker you might check comments/commit msg. I'm not native speaker so it is hard for me, but honestly never heard word "superjacent" (for example) and "Currently it means checking that login user/group indeed exists," also looks suspicious (I would personally use "really" instead of "indeed"). It just doesn't sound for me like native English.

Anyway, I you think comments/commit msg is ok I will just give it formal ack right then.

@clumens
Copy link
Author

clumens commented Jul 10, 2024

I've checked commits twice and it looks there is no obvious problem codewise, but because you are native English speaker you might check comments/commit msg. I'm not native speaker so it is hard for me, but honestly never heard word "superjacent" (for example) and "Currently it means checking that login user/group indeed exists," also looks suspicious (I would personally use "really" instead of "indeed"). It just doesn't sound for me like native English.

I had to look it up and "superjacent" is a word. I've never heard it either.

I was trying to keep the commit messages the same to stay as close to the original commit (and original authorship) as possible, but perhaps I should go ahead and reword them to be a little easier to understand. I'm not sure if I should just make new commits with me as the author and somehow credit poki in the commit message, or what.

clumens and others added 2 commits July 10, 2024 15:04
...as well as functions it calls and functions that call it.

Co-authored-by: Jan Pokorný <[email protected]>
@clumens
Copy link
Author

clumens commented Jul 10, 2024

Updated with new commit messages and comment for check_config, changed the author to myself (I've made various changes in this PR, I hope this is okay), and added poki as Co-authored-by. If this looks good, this is the process I'll use going forward. This is ready for ACK/NAK.

Copy link
Member

@jfriesse jfriesse left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perfect, thanks, now it looks like English and much easier to understand. I think Co-authored is good idea so ACK.

@clumens clumens merged commit dc165ea into ClusterLabs:main Jul 11, 2024
1 check passed
@clumens clumens deleted the cfg-globals branch July 11, 2024 13:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants