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

Really minor typo in the doc #630

Merged
merged 2 commits into from
Apr 1, 2024
Merged

Really minor typo in the doc #630

merged 2 commits into from
Apr 1, 2024

Conversation

fgrosshans
Copy link

A dash was missing between 𝔸 and β„€ in the description of the range of the double-struck style: it was {𝕒–𝕫,𝔸℀}

fgrosshans and others added 2 commits February 14, 2024 19:21
A dash was missing between 𝔸 and β„€ in the description of the range of the double-struck style: it was {𝕒–𝕫,𝔸℀}
Really minor typo in the doc
@davidcarlisle
Copy link
Member

Thanks for the PR, which is obviously correct except I'm not sure about the status of the target branch. @wspr do you use the working branch for staging or is that now redundant and feature branch PR can go straight to master (which we probably should rename to main)?

@wspr
Copy link
Collaborator

wspr commented Apr 1, 2024

@davidcarlisle β€” it still suits my workflow to have commits turn up here but in the long run I think we should just go with the main branch. I'll change the GitHub setting for where pull requests should land

@wspr
Copy link
Collaborator

wspr commented Apr 1, 2024

Hmm, I must have been dreaming when I thought there was a setting for that... never mind

@wspr wspr merged commit 6beba2b into latex3:working Apr 1, 2024
@fgrosshans fgrosshans deleted the working branch May 15, 2024 15:45
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 this pull request may close these issues.

None yet

3 participants