[Keyboard] Relocalize and Update p1800fl

[team0110]

Description

We are currently in Production Stage, so i could like to relocalize p1800fl to desired folder, also update VIA keymap

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).

[team0110]

Thank for your advise @fauxpark

[drashna]

Since this is moving the board's location, it should target the develop branch.

[marhalloweenvt]

Since this is moving the board's location, it should target the develop branch.

Thank for your reply, @drashna .
Does it mean i need to commit it in Dev Bracnh? And how long will it take to be merged in master branch?

[drashna]

Since this is moving the board's location, it should target the develop branch.

Thank for your reply, @drashna .
Does it mean i need to commit it in Dev Bracnh? And how long will it take to be merged in master branch?

It would be targeted to and merged into develop, yes. And the timeline is:
https://docs.qmk.fm/#/breaking_changes?id=important-dates

So a month before it hit master.

[tzarc]

Apparently there's now a conflict.

[marhalloweenvt]

Apparently there's now a conflict.

How can I help you to resolve the conflict? From my side, I can't see any recommends.

[drashna]

Apparently there's now a conflict.

How can I help you to resolve the conflict? From my side, I can't see any recommends.

You'd need to rebase the branch, I think.

[stale]

Thank you for your contribution!
This pull request has been automatically marked as stale because it has not had activity in the last 45 days. It will be closed in 30 days if no further activity occurs. Please feel free to give a status update now, or re-open when it's ready.
For maintainers: Please label with awaiting review, breaking_change, in progress, or on hold to prevent the issue from being re-flagged.

[drashna]

Thanks!

And I fixed up the merge conflicts for you.
Mostly, it's just git merge upstream/develop and fix the conflicts. (that or git rebase upstream/develop)

[marhalloweenvt]

Thanks!

And I fixed up the merge conflicts for you.
Mostly, it's just git merge upstream/develop and fix the conflicts. (that or git rebase upstream/develop)

Thanks for your kind support. If there is any issues, please let me know.