undefined | Better HN

0 pointsjasonvorhe25d ago0 comments

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

0 comments

3 comments · 1 top-level

fooker25d ago· 2 in thread

Figuring out which commit broke what functionality is not something you can expect users to do.

Lerc24d ago

No, but that's probably a required skill to have before you initiate claims as to what the cause of the loss of functionality was.

cbarnes9924d ago

If you're willing to build from source it's not particularly difficult with git bisect

j / k navigate · click thread line to collapse