[–] johnb 12y ago ↗ That is some mean-spirited internetting right there.From the title I was hoping it was a 500 page that git blames the backtrace and tells the user who specifically messed up. [–] ryalfalpha 12y ago ↗ That's a fascinating idea, even if it's not made public to the end user. Getting the git blamed stacktraces mailed to the dev team would be interesting! [–] thedudemabry 12y ago ↗ Hahaha! It's definitely evil, but a funny evil.
[–] ryalfalpha 12y ago ↗ That's a fascinating idea, even if it's not made public to the end user. Getting the git blamed stacktraces mailed to the dev team would be interesting! [–] thedudemabry 12y ago ↗ Hahaha! It's definitely evil, but a funny evil.
[–] officialjunk 12y ago ↗ Looks like it thinks my iOS chrome is safari. The demo does not look at all like a chrome Internet connection error screen
5 comments
[ 13.4 ms ] story [ 20.2 ms ] threadFrom the title I was hoping it was a 500 page that git blames the backtrace and tells the user who specifically messed up.