move @latincompass (aka @18438880 , @haierwangwei2005)'s boards to /latincompass #16039
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
keyboard
keymap
via
|
Thanks a Lot,Sir,I appreciate your work. |
|
The 18438880 and haierwangwei2005 two Account is also my Account |
latincompass
approved these changes
Jan 25, 2022
haierwangwei2005
approved these changes
Jan 25, 2022
|
Thank you for your hard work,Sir I have Approve it in latincompass 18438880 haierwangwei2005 those 3 Accounts .
…------------------ 原始邮件 ------------------
发件人: "qmk/qmk_firmware" ***@***.***>;
发送时间: 2022年1月25日(星期二) 晚上11:41
***@***.***>;
***@***.******@***.***>;
主题: [qmk/qmk_firmware] move @latincompass (aka @18438880 , @haierwangwei2005)'s boards to /latincompass (PR #16039)
Description
At this point in my series of board move PRs, I've started to move boards where I cannot reach the makers beforehand, and have to contact them via the PR itself.
This PR is made without contacting(or failing at contacting) @latincompass ( @18438880 , @haierwangwei2005 ) first, so it would need them to approve it for it to go in.
One of the reasons I'm electing to do this is to get as many PRs in as possible before the breaking change deadline, please stop me in my tracks if this is inappropriate.
Types of Changes
Core
Bugfix
New feature
Enhancement/optimization
Keyboard (addition or update)
Keymap/layout/userspace (addition or update)
Documentation
Issues Fixed or Closed by This PR
Checklist
My code follows the code style of this project: C, Python
I have read the PR Checklist document and have made the appropriate changes.
My change requires a change to the documentation.
I have updated the documentation accordingly.
I have read the CONTRIBUTING document.
I have added tests to cover my changes.
I have tested the changes and verified that they work and don't break anything (as well as I can manage).
You can view, comment on, or merge this pull request online at:
#16039
Commit Summary
aa068fe move @latincompass (aka @18438880 , @haierwangwei2005)'s boards to /latincompass
File Changes
(65 files)
R keyboards/latincompass/latin17rgb/config.h (0)
R keyboards/latincompass/latin17rgb/info.json (0)
R keyboards/latincompass/latin17rgb/keymaps/default/keymap.c (0)
R keyboards/latincompass/latin17rgb/keymaps/via/keymap.c (0)
R keyboards/latincompass/latin17rgb/keymaps/via/rules.mk (0)
R keyboards/latincompass/latin17rgb/latin17rgb.c (0)
R keyboards/latincompass/latin17rgb/latin17rgb.h (0)
R keyboards/latincompass/latin17rgb/readme.md (4)
R keyboards/latincompass/latin17rgb/rules.mk (0)
R keyboards/latincompass/latin47ble/config.h (0)
R keyboards/latincompass/latin47ble/info.json (0)
R keyboards/latincompass/latin47ble/keymaps/default/keymap.c (0)
R keyboards/latincompass/latin47ble/keymaps/via/keymap.c (0)
R keyboards/latincompass/latin47ble/keymaps/via/rules.mk (0)
R keyboards/latincompass/latin47ble/latin47ble.c (0)
R keyboards/latincompass/latin47ble/latin47ble.h (0)
R keyboards/latincompass/latin47ble/readme.md (2)
R keyboards/latincompass/latin47ble/rules.mk (0)
R keyboards/latincompass/latin60rgb/config.h (0)
R keyboards/latincompass/latin60rgb/info.json (0)
R keyboards/latincompass/latin60rgb/keymaps/default/keymap.c (0)
R keyboards/latincompass/latin60rgb/keymaps/via/keymap.c (0)
R keyboards/latincompass/latin60rgb/keymaps/via/rules.mk (0)
R keyboards/latincompass/latin60rgb/latin60rgb.c (0)
R keyboards/latincompass/latin60rgb/latin60rgb.h (0)
R keyboards/latincompass/latin60rgb/readme.md (2)
R keyboards/latincompass/latin60rgb/rules.mk (0)
R keyboards/latincompass/latin64ble/config.h (0)
R keyboards/latincompass/latin64ble/info.json (0)
R keyboards/latincompass/latin64ble/keymaps/default/keymap.c (0)
R keyboards/latincompass/latin64ble/keymaps/via/keymap.c (0)
R keyboards/latincompass/latin64ble/keymaps/via/rules.mk (0)
R keyboards/latincompass/latin64ble/latin64ble.c (0)
R keyboards/latincompass/latin64ble/latin64ble.h (0)
R keyboards/latincompass/latin64ble/readme.md (2)
R keyboards/latincompass/latin64ble/rules.mk (0)
R keyboards/latincompass/latin6rgb/config.h (0)
R keyboards/latincompass/latin6rgb/info.json (0)
R keyboards/latincompass/latin6rgb/keymaps/default/keymap.c (0)
R keyboards/latincompass/latin6rgb/keymaps/via/keymap.c (0)
R keyboards/latincompass/latin6rgb/keymaps/via/rules.mk (0)
R keyboards/latincompass/latin6rgb/latin6rgb.c (0)
R keyboards/latincompass/latin6rgb/latin6rgb.h (0)
R keyboards/latincompass/latin6rgb/readme.md (2)
R keyboards/latincompass/latin6rgb/rules.mk (0)
R keyboards/latincompass/latinpad/config.h (0)
R keyboards/latincompass/latinpad/info.json (0)
R keyboards/latincompass/latinpad/keymaps/default/keymap.c (0)
R keyboards/latincompass/latinpad/keymaps/via/keymap.c (0)
R keyboards/latincompass/latinpad/keymaps/via/rules.mk (0)
R keyboards/latincompass/latinpad/latinpad.c (0)
R keyboards/latincompass/latinpad/latinpad.h (0)
R keyboards/latincompass/latinpad/lib/glcdfont.c (0)
R keyboards/latincompass/latinpad/readme.md (2)
R keyboards/latincompass/latinpad/rules.mk (0)
R keyboards/latincompass/latinpadble/config.h (0)
R keyboards/latincompass/latinpadble/info.json (0)
R keyboards/latincompass/latinpadble/keymaps/default/keymap.c (0)
R keyboards/latincompass/latinpadble/keymaps/via/keymap.c (0)
R keyboards/latincompass/latinpadble/keymaps/via/rules.mk (0)
R keyboards/latincompass/latinpadble/latinpadble.c (0)
R keyboards/latincompass/latinpadble/latinpadble.h (0)
R keyboards/latincompass/latinpadble/lib/glcdfont.c (0)
R keyboards/latincompass/latinpadble/readme.md (2)
R keyboards/latincompass/latinpadble/rules.mk (0)
Patch Links:
https://github.com/qmk/qmk_firmware/pull/16039.patch
https://github.com/qmk/qmk_firmware/pull/16039.diff
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
|
Merge conflicts |
peepeetee
force-pushed
the
latincompass
branch
from
aa068fe to
99b3890
Compare
…atincompass
peepeetee
force-pushed
the
latincompass
branch
from
99b3890 to
64852f7
Compare
resolved |
zvecr
approved these changes
Feb 10, 2022
drashna
approved these changes
Feb 10, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
At this point in my series of board move PRs, I've started to move boards where I cannot reach the makers beforehand, and have to contact them via the PR itself.
This PR is made without contacting(or failing at contacting) @latincompass ( @18438880 , @haierwangwei2005 ) first, so it would need them to approve it for it to go in.
As there was no prior communication before this PR, I have to ask a few questions:
One of the reasons I'm electing to do this is to get as many PRs in as possible before the breaking change deadline, please stop me in my tracks if this is inappropriate.
Types of Changes
Issues Fixed or Closed by This PR
Checklist