Re:Fp8 runs ~100 tflops faster when the kernel name has "cut...
by kristopolous on Friday October 03, 2025 @02:43AM
(#45459784)
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
[ Parent
| on HN ]
Re:Fp8 runs ~100 tflops faster when the kernel name has "cut...
by lloeki on Friday October 03, 2025 @03:55AM
(#45460249)
> you can only delete the human input once
git branch "backup/$(git branch --show-current)/$(date +%s)"
# do whatever you fancy
git reset --hard "backup/$(git branch --show-current)/${thattimestampabove}"
You can't lose anything as long as you have a pointer to it (which doubles as making it easy to find)
Re:Fp8 runs ~100 tflops faster when the kernel name has "cut...
by globular-toast on Friday October 03, 2025 @04:25AM
(#45460442)
No need to make a "backup" branch. Learn to trust the reflog.
Re:Fp8 runs ~100 tflops faster when the kernel name has "cut...
by lemonlearnings on Friday October 03, 2025 @08:08AM
(#45461999)
That is like learn to trust the indestructibility of matter. I can still lose (not able to locate...) my keys even though they still exist!
Re:Fp8 runs ~100 tflops faster when the kernel name has "cut...
by lloeki on Monday October 06, 2025 @03:40AM
(#45488665)
reflog doesn't keep things through gc.
the only thing that does keep a git object is having a ref that (directly or transitively) points to it
Re:Fp8 runs ~100 tflops faster when the kernel name has "cut...
by trenchpilgrim on Friday October 03, 2025 @02:59AM
(#45459884)
My human inputs are usually commit messages like "awdjhwahdwadga" until I do the rebase at the end
Re:Fp8 runs ~100 tflops faster when the kernel name has "cut...
by lemonlearnings on Friday October 03, 2025 @07:59AM
(#45461924)
? I assume you want to replace your jubberish messages with something more useful before pushing? It is only "destroying"
https://xkcd.com/1296/ style crap? Code changes stay the same.