Alex Moes sorry, but is better to summarize:
-(C) does "a" wrong merge. {It happens! nothing serious! not too often though, I recommend:}
-user kindly notifies (C) of the error, and that the sources are in the close BRO documented historical VIP.
-(C) go offline.
-(C) online, unresponsive and continues with its hundreds of daily merge.
-user remember notification.
-(C) offline.
-user fixes by himself and communicates that no more intervention is needed.
-another (C) hides the aforementioned message and begins a spiral of increasingly gloomy communications:
*now with the last one talking about "(C) not being paid doesn't necessarily have to fix what (C) broke!?" {{{who cares if (C) doesn't talk to me, just FIX for (C) mistake}}}
(I know you will say NO, at least I hope so, otherwise the spiral could lead to an inevitable: "if (X) don't pay (Y) ruin things and (Z) shut up" ..and this would be immoral? criminal ? prosecutable? agree?
We all make mistakes, some more, some less, letting them know is the only way to stop the spiral of mistakes. It can make someone unpopular but it must be done.