Skip to content

Conversation

@Ledest
Copy link

@Ledest Ledest commented Jul 22, 2017

No description provided.

@fishballian
Copy link

Good job!

@ericbmerritt
Copy link
Member

@Ledest are you still interested in merging this?

@Ledest
Copy link
Author

Ledest commented May 13, 2019

@Ledest are you still interested in merging this?

@Ledest Ledest closed this May 13, 2019
@Ledest Ledest reopened this May 13, 2019
@Ledest
Copy link
Author

Ledest commented May 13, 2019

@Ledest are you still interested in merging this?

Yes, but I requested 3 first commits only, not 21 commits.

@ericbmerritt
Copy link
Member

ericbmerritt commented May 13, 2019 via email

@saleyn
Copy link
Collaborator

saleyn commented Nov 7, 2022

@Ledest, could you squash your commits, and fix conflicts?

@saleyn
Copy link
Collaborator

saleyn commented Dec 13, 2022

It is a pretty stale PR. Could you review and see if it's still necessary given the existing changes in the master branch since the time this PR was created?

@saleyn
Copy link
Collaborator

saleyn commented Jan 3, 2023

@Ledest, could you resolve conflicts, please, and split this into two PRs - one fixing the actual issue in the subject along with test cases, and one for other minor improvements?

@saleyn
Copy link
Collaborator

saleyn commented May 21, 2023

@Ledest, could you rebase on master? This PR has very many conflicts.

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.

4 participants