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
Add support for Acer XV273K (ACR06B1) #114
Conversation
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.
Seems good.
Please, remove duplicate controls from VESA profile, and only include the VESA profile:
<include file="VESA"/>
Thanks for your reply! I'm as strong of a DRY advocate as they come, so I appreciate your feedback regarding the VESA profile. IIRC, there was actually a legit reason why I chose not to include it, but I'll have to get back to you once I get home. Hopefully I can find a more DRY solution. 🙂 |
Alright, @kravemir. The reason why I didn't include the VESA profile was because then I couldn't get rid of the Secondary Degauss control (which isn't supported by XV273K and makes no sense for an LCD monitor anyway). Surprisingly, while the presence or absence of These statements are true of the output of
|
I'd also like to suggest squashing PRs instead of creating merge commits, even though the latter happened to help me out this time. |
@SimonAlling thank you for the effort you've spent preparing this PR, and applying the comment, good job! I'm sorry for not responding before, and not directing you at the possibility to remove caps using
That's a good idea. Also, github complains "This branch is out-of-date with the base branch", so it would be nice, if you could merge the latest And, as I'm not a maintainer anymore, @larstobi could take over, and merge it. |
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.
LGTM
Thanks!
Thanks for the suggestion! Why would you like squashing PRs? I think merge commits are useful in that they give a link to the PR, which often contains much information. I do realize that they create a non-linear history. |
Because in the Git log for Also tends to make the log easier to read in general. Tip right now:
So do squash commits. See for example this one. |
No worries!
Surprisingly, removing |
@SimonAlling I agree. I've configured this repo to only allow Squash from now on. Thanks! |
No description provided.