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 rename migration to example users: System -> system #55

Merged
merged 3 commits into from
Aug 25, 2023

Conversation

sksat
Copy link
Member

@sksat sksat commented Aug 3, 2023

概要

System -> system への migration を example user に適用した

Issue / PR

@sksat sksat added enhancement New feature or request priority::high priorityg high labels Aug 3, 2023
@sksat sksat self-assigned this Aug 3, 2023
@sksat
Copy link
Member Author

sksat commented Aug 3, 2023

これ S2E に対して breaking だな

@meltingrabbit
Copy link
Member

これ S2E に対して breaking だな

どうしよ.

S2E core ?

user なら S2E for minimum user を fork なんですが.

@sksat
Copy link
Member Author

sksat commented Aug 3, 2023

  • 一旦壊れてるの許容して c2a-core beta release -> s2e-core に修正 -> c2a-core の S2E CI を修正
  • s2e-core に修正 -> c2a-core の S2E CI を修正(パッチ出したやつを参照) -> s2e-core update -> c2a-core の S2E CI を released version に書き換え

のどっちかかな

@sksat
Copy link
Member Author

sksat commented Aug 3, 2023

ただここで問題なのは,当然 s2e-core に対する修正は c2a-core v3 に対して breaking

@sksat
Copy link
Member Author

sksat commented Aug 3, 2023

ただここで問題なのは,当然 s2e-core に対する修正は c2a-core v3 に対して breaking

あいや,これは c2a_core_main.h を include して major version で ifdef すればいいか?

@meltingrabbit
Copy link
Member

今,さまざまなbrakingをやってるので,CIがコケてる状態でマージはしたくないなぁ.
すぐ解消されるならまあ許容はできる

@meltingrabbit
Copy link
Member

これ,S2E userのみでは解消不能なんだっけ?(s2e-core修正必須?)

@sksat
Copy link
Member Author

sksat commented Aug 4, 2023

s2e-core problem ですね

@sksat
Copy link
Member Author

sksat commented Aug 4, 2023

むしろ S2E user は修正要らないな

@meltingrabbit
Copy link
Member

ただここで問題なのは,当然 s2e-core に対する修正は c2a-core v3 に対して breaking

あいや,これは c2a_core_main.h を include して major version で ifdef すればいいか?

これやるしかなさそう?
AOBCは当面v3系列使いそうですし.

@sksat sksat force-pushed the feature/rename-system-examples branch from 3841e89 to c3cb18d Compare August 25, 2023 08:14
@sksat
Copy link
Member Author

sksat commented Aug 25, 2023

#54 を更新したので rebase

@sksat sksat force-pushed the feature/rename-system-examples branch from fec492c to 293d4b5 Compare August 25, 2023 08:35
@sksat
Copy link
Member Author

sksat commented Aug 25, 2023

正しく re-run するために force push(c2a-enum-loader 対応)

Copy link
Member

@meltingrabbit meltingrabbit left a comment

Choose a reason for hiding this comment

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

めでたい

Base automatically changed from feature/rename-system-dir-to-snake-case to develop August 25, 2023 08:46
@sksat sksat merged commit d65d896 into develop Aug 25, 2023
35 checks passed
@sksat sksat deleted the feature/rename-system-examples branch August 25, 2023 08:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request priority::high priorityg high
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

2 participants