-
Notifications
You must be signed in to change notification settings - Fork 14
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
Allow to comment out or uncomment a macro definition #298
Conversation
Build succeeded. ✔️ pre-commit SUCCESS in 1m 51s |
Why not use the |
Mainly because nobody uses |
Well, if you're adding a commented_out property, |
Ok, I suppose it would make sense to add another property, let's say |
fc4bf9c
to
9c4d01d
Compare
Build succeeded. ✔️ pre-commit SUCCESS in 1m 54s |
Maybe have one |
Signed-off-by: Nikola Forró <[email protected]>
9c4d01d
to
21027a3
Compare
Build succeeded. ✔️ pre-commit SUCCESS in 2m 05s |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like the approach with multiple styles.
Build succeeded (gate pipeline). ✔️ pre-commit SUCCESS in 1m 43s |
Necessary for Packit to be able to comment out or uncomment a pre-release suffix macro definition (example).
Related to packit/packit#2013.
RELEASE NOTES BEGIN
Macro definitions gained a new
commented_out
property indicating that a macro definition is commented out. Another new property,comment_out_style
, determines if it is achieved by using a%dnl
(discard next line) directive (e.g.%dnl %global prerelease beta2
) or by replacing the starting%
with#
(e.g.#global prerelease beta2
).RELEASE NOTES END