I'm confused why the correct course of action isn't to revert the commit, ask the author to re-open the PR for comment, and follow the process. Why the tortious apology?
I'm sorry
11–20 of 277 posts
Re: I'm sorry
#12I'm confused why the correct course of action isn't to revert the commit, ask the author to re-open the PR for comment, and follow the process. Why the tortious apology?
Because attention seeking...
Re: I'm sorry
#13I'm confused why the correct course of action isn't to revert the commit, ask the author to re-open the PR for comment, and follow the process. Why the tortious apology?
"There is a pattern that needs to be resolved. Projects might not fully understand what joining the .NET Foundation means..."
This sounds like not only an apology, but an attempt to start a discussion surrounding the community overall and get everyone to have matching expectations.
Re: I'm sorry
#14Re: I'm sorry
#15holy fuck, does every little mistake need a solemn 4000 word apology these days? that’s already not a world i want to live in, but then even the apology gets shit on and invalidated. people need to take everything much less seriously, especially shit that happens on the internet. this whole thing should have been able to be a new PR with “sorry about the merge before, i screwed up and it won’t happen again” at the en…
Saying "sorry" just isn't enough to absolve your "misdeeds", whatever they might be.
Re: I'm sorry
#16holy fuck, does every little mistake need a solemn 4000 word apology these days? that’s already not a world i want to live in, but then even the apology gets shit on and invalidated. people need to take everything much less seriously, especially shit that happens on the internet. this whole thing should have been able to be a new PR with “sorry about the merge before, i screwed up and it won’t happen again” at the en…
Edit: as lots of people said, I was on an older version of the file. I'm not sure how I did this, but I should have double-checked, especially since there was some base64 stuff in the URL.
Re: I'm sorry
#17holy fuck, does every little mistake need a solemn 4000 word apology these days? that’s already not a world i want to live in, but then even the apology gets shit on and invalidated. people need to take everything much less seriously, especially shit that happens on the internet. this whole thing should have been able to be a new PR with “sorry about the merge before, i screwed up and it won’t happen again” at the en…
Re: I'm sorry
#18Re: I'm sorry
#19Re: I'm sorry
#20holy fuck, does every little mistake need a solemn 4000 word apology these days? that’s already not a world i want to live in, but then even the apology gets shit on and invalidated. people need to take everything much less seriously, especially shit that happens on the internet. this whole thing should have been able to be a new PR with “sorry about the merge before, i screwed up and it won’t happen again” at the en…
I think the apology is here because the author of the PR doesn't want to revert it. As you can see, it's still merged: https://github.com/reactiveui/splat/blob/b930a34badfb2164f38... Edit: as lots of people said, I was on an older version of the file. I'm not sure how I did this, but I should have double-checked, especially since there was some base64 stuff in the URL.
Sorry not sorry.