Thanks to visit codestin.com
Credit goes to github.com

Skip to content

DOC: Clarify terminology #26257

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

Merged
merged 1 commit into from
Jul 4, 2023
Merged

Conversation

StefRe
Copy link
Contributor

@StefRe StefRe commented Jul 4, 2023

PR summary

The objects to locate ticks are called locators. They are defined in the modules ticker and dates.

xref #26254 (review)

PR checklist

The objects to locate ticks are called locators. They are defined in the
modules ticker and dates.
@jklymak jklymak added this to the v3.7-doc milestone Jul 4, 2023
@jklymak jklymak merged commit 1d78f12 into matplotlib:main Jul 4, 2023
@lumberbot-app
Copy link

lumberbot-app bot commented Jul 4, 2023

Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

  1. Checkout backport branch and update it.
git checkout v3.7.x
git pull
  1. Cherry pick the first parent branch of the this PR on top of the older branch:
git cherry-pick -x -m1 1d78f1299945169f3792f0b9fc9b3fe62786feaf
  1. You will likely have some merge/cherry-pick conflict here, fix them and commit:
git commit -am 'Backport PR #26257: DOC: Clarify terminology'
  1. Push to a named branch:
git push YOURFORK v3.7.x:auto-backport-of-pr-26257-on-v3.7.x
  1. Create a PR against branch v3.7.x, I would have named this PR:

"Backport PR #26257 on branch v3.7.x (DOC: Clarify terminology)"

And apply the correct labels and milestones.

Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon!

Remember to remove the Still Needs Manual Backport label once the PR gets merged.

If these instructions are inaccurate, feel free to suggest an improvement.

@lumberbot-app
Copy link

lumberbot-app bot commented Jul 4, 2023

Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

  1. Checkout backport branch and update it.
git checkout v3.7.1-doc
git pull
  1. Cherry pick the first parent branch of the this PR on top of the older branch:
git cherry-pick -x -m1 1d78f1299945169f3792f0b9fc9b3fe62786feaf
  1. You will likely have some merge/cherry-pick conflict here, fix them and commit:
git commit -am 'Backport PR #26257: DOC: Clarify terminology'
  1. Push to a named branch:
git push YOURFORK v3.7.1-doc:auto-backport-of-pr-26257-on-v3.7.1-doc
  1. Create a PR against branch v3.7.1-doc, I would have named this PR:

"Backport PR #26257 on branch v3.7.1-doc (DOC: Clarify terminology)"

And apply the correct labels and milestones.

Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon!

Remember to remove the Still Needs Manual Backport label once the PR gets merged.

If these instructions are inaccurate, feel free to suggest an improvement.

@StefRe StefRe deleted the fix/locator-ticker-wording branch July 4, 2023 20:28
@QuLogic QuLogic modified the milestones: v3.7-doc, v3.8.0 Jul 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants