Keeping it real with the commit msgs
I much prefer this over those AI generated commit messages that just say "refactored X" every single commit.
So AI really does learn from humans...
Fp8 runs ~100 tflops faster when the kernel name has "cutlass" in it
11–20 of 176 posts
Re: Fp8 runs ~100 tflops faster when the kernel name has "cutlass" in it
#12Someone really needs to learn to use `git commit --amend`. Almost 100 commits with pointless commit messages like "wip" or "x"? Be kinder to your reviewers...
Re: Fp8 runs ~100 tflops faster when the kernel name has "cutlass" in it
#13This was discussed before at the time the PR was created and there's nothing new that I can see. https://news.ycombinator.com/item?id=44530581
Thought this looked familiar...
Re: Fp8 runs ~100 tflops faster when the kernel name has "cutlass" in it
#14Someone really needs to learn to use `git commit --amend`. Almost 100 commits with pointless commit messages like "wip" or "x"? Be kinder to your reviewers...
and
git commit --fixup
git rebase -i --autosquash
Re: Fp8 runs ~100 tflops faster when the kernel name has "cutlass" in it
#15Keeping it real with the commit msgs
I think it's fine if you squash it. I have no idea why they didn't squash it before pushing to GitHub though.
Re: Fp8 runs ~100 tflops faster when the kernel name has "cutlass" in it
#16Someone really needs to learn to use `git commit --amend`. Almost 100 commits with pointless commit messages like "wip" or "x"? Be kinder to your reviewers...
and git commit --fixup git rebase -i --autosquash
Claude, look at this git history, analyse diffs and create an intelligent commit message to replace each commit message. Do a rebase to fix it all up.
Re: Fp8 runs ~100 tflops faster when the kernel name has "cutlass" in it
#17Heh. Does anyone remember when almost 25 years ago ATI (AMD) caught manipulating the Quake III benchmarks by renaming the executables to ‘quack’?
https://web.archive.org/web/20230929180112/https://techrepor...
https://web.archive.org/web/20011108190056/https://hardocp.c...
https://web.archive.org/web/20011118183932/www.3dcenter.de/a...
Re: Fp8 runs ~100 tflops faster when the kernel name has "cutlass" in it
#18Earlier quoted context omitted.
and git commit --fixup git rebase -i --autosquash
Claude, look at this git history, analyse diffs and create an intelligent commit message to replace each commit message. Do a rebase to fix it all up.
Would you actually do that? It's information destruction. You can machine generate at any time, but you can only delete the human input once
Re: Fp8 runs ~100 tflops faster when the kernel name has "cutlass" in it
#19Re: Fp8 runs ~100 tflops faster when the kernel name has "cutlass" in it
#20Earlier quoted context omitted.
Claude, look at this git history, analyse diffs and create an intelligent commit message to replace each commit message. Do a rebase to fix it all up.
Would you actually do that? It's information destruction. You can machine generate at any time, but you can only delete the human input once
My human inputs are usually commit messages like "awdjhwahdwadga" until I do the rebase at the end