Re:Rsync 3.4.3 has hundreds of Claude commits
by omgtehlion on Saturday May 30, 2026 @05:09AM
(#48334226)
Seems like 3.4.2 was already vibe-maintained: https://github.com/RsyncProject/rsync/commits/v3.4.2
[ Parent
| on HN ]
Re:Rsync 3.4.3 has hundreds of Claude commits
by kelnos on Saturday May 30, 2026 @05:20AM
(#48334294)
It's pretty shitty to accuse someone of vibe-coding without having any idea what their LLM-assisted development process is. Let's do better, please.
Re:Rsync 3.4.3 has hundreds of Claude commits
by jasonvorhe on Saturday May 30, 2026 @05:20AM
(#48334293)
So? May main point is: Which commits actually broke the functionality? Going from 3.4.3 to 3.4.2 to test should be easy for anyone affected and would have been more helpful than this rant.
I'm not defending bad slop commits, especially for such a long running project but the tribal Fediverse outrage whenever LLMs are involved is often just lazy and uninformed.
To quote this PR: https://github.com/RsyncProject/rsync/issues/928
> NOTE: This also affects backported rsync versions when they're used on the Receiver: > Debian: 3.4.1+ds1-5+deb13u3 / 3.2.7-1+deb12u5 / 3.2.3-4+deb11u3 > Ubuntu: 3.2.7-1ubuntu1.4
Re:Rsync 3.4.3 has hundreds of Claude commits
by fooker on Saturday May 30, 2026 @05:39AM
(#48334396)
Figuring out which commit broke what functionality is not something you can expect users to do.