Skip to content

Conversation

@everpcpc
Copy link

An updated version for #1196

@everpcpc everpcpc force-pushed the KAFKA-1614 branch 3 times, most recently from 1dac0ea to 2d9f360 Compare August 8, 2018 03:44
@DarrenBishop
Copy link

What's the process for getting this (and perhaps its predecessor) PRs merged?
What needs to be addressed with the build checks?

@everpcpc
Copy link
Author

everpcpc commented Nov 7, 2018

The build check error seems not related to the changes.

@vykimo
Copy link

vykimo commented May 28, 2019

still not on master branch?

@m1losz
Copy link

m1losz commented Aug 15, 2019

is this gonna get merged to master soon?

@github-actions
Copy link

This PR is being marked as stale since it has not had any activity in 90 days. If you
would like to keep this PR alive, please leave a comment asking for a review. If the PR has
merge conflicts, update it with the latest from the base branch.

If you are having difficulty finding a reviewer, please reach out on the [mailing list](https://kafka.apache.org/contact).

If this PR is no longer valid or desired, please feel free to close it. If no activity occurs in the next 30 days, it will be automatically closed.

@github-actions github-actions bot added the stale Stale PRs label Nov 17, 2024
@github-actions
Copy link

This PR has been closed since it has not had any activity in 120 days. If you feel like this
was a mistake, or you would like to continue working on it, please feel free to re-open the
PR and ask for a review.

@github-actions github-actions bot added the closed-stale PRs that were closed due to inactivity label Dec 17, 2024
@github-actions github-actions bot closed this Dec 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

closed-stale PRs that were closed due to inactivity stale Stale PRs

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants