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

Unify Tonel format #357

Open
JanBliznicenko opened this issue Jun 18, 2024 · 1 comment
Open

Unify Tonel format #357

JanBliznicenko opened this issue Jun 18, 2024 · 1 comment

Comments

@JanBliznicenko
Copy link
Contributor

JanBliznicenko commented Jun 18, 2024

Pharo 12 generates Tonel 3.0, Pharo 11 generates Tonel 1.0.

Whenever any part of a class is changed in Pharo 12, the format of the entire is rewritten to Tonel 3.0, making quite a noise in commits.
The format should be unified in a single commit. Either by forcing update to Tonel 3.0, or specifying that Tonel 1.0 should be kept.

Moving to Tonel 3.0 might be preferrable as it is better compatible with GemStone and both versions are compatible.

@seandenigris
Copy link
Member

Please see my comment on #358

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants