-
Notifications
You must be signed in to change notification settings - Fork 635
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
Helping on 571 #572
Comments
@francescov1 Reading through the comments, it seems to me that you were being very friendly and more like intending to spend as much time as possible to solve the issue, or emphasizing it's an issue that has a high impact on user side. I dont see you were rushing the maintainer in any way. |
@mgenware Sorry but I disagree. Being friendly or not is not the problem here. You can be the kindest person on earth. However, when you ask maintainer's input to resolve an issue ASAP and mention that a release depends on it, what do you expect maintainer to feel? |
Hi @tanersener , I forgot to mention that I totally understand your point in that thread as well, and I'm so grateful that you've put so much personal time on such a great project that benefits a ton of people in the world. You are right, I can feel what you said :-D |
Alright. Let's move on. The bug was fixed. That's the most important thing. And, thanks for reporting these issues. That's how we can make this library better. |
There was a misunderstanding in my previous issue, https://github.com/tanersener/ffmpeg-kit/issues/571.
I was hoping to help resolve the bug, and was trying to probe for more information about what the root problem was. I had no intention to rush the maintainers to fix it, just wanted to know where to start on the problem. Apologies for the misunderstanding.
It would be great if the issue could be unlocked so we can discuss it. Feel free to close this current issue.
The text was updated successfully, but these errors were encountered: