Skip to content

term: must vs. should (BAD)#1687

Closed
jorgeorpinel wants to merge 26 commits into
masterfrom
term/must-should
Closed

term: must vs. should (BAD)#1687
jorgeorpinel wants to merge 26 commits into
masterfrom
term/must-should

Conversation

@jorgeorpinel
Copy link
Copy Markdown
Contributor

Non-extensive in the case of "should" — there's too many instances.

+ some copy edits around the instances I did review

@shcheklein shcheklein temporarily deployed to dvc-landing-term-must-s-xi0tj3 August 11, 2020 18:11 Inactive
@@ -0,0 +1,8 @@
---
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

unrelated change?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Shoot. This is from another PR (#1680)...

@shcheklein
Copy link
Copy Markdown
Contributor

it looks like we have a mix of changes in this PR, please clean it up first a bit

@jorgeorpinel
Copy link
Copy Markdown
Contributor Author

Something very wrong happened with the branching here... Sorry

@jorgeorpinel jorgeorpinel changed the title term: must vs. should term: must vs. should (BAD) Aug 12, 2020
@jorgeorpinel
Copy link
Copy Markdown
Contributor Author

Trying again in #1692.

@jorgeorpinel jorgeorpinel deleted the term/must-should branch August 13, 2020 17:42
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.

2 participants