News for hackers. Stuff that matters.

A comment on Rietveld - code review Google style. Parent comment

Re:Rietveld - code review Google style by brown9-2 on Friday February 11, 2011 @03:44PM (#2208050)
If you do not sync and test your changes against the latest, I'd argue that you're being careless - how do you know things still interact properly?

This would suggest that the developer who checked in changes to A, which is used by B, did not also make the changes to B so that it works with the changes to A. That seems to be the actual careless action to me.

[ Parent | on HN ]
Re:Rietveld - code review Google style by groby_b on Wednesday February 16, 2011 @11:01AM (#2226886)
The point of "sync & test before commit" is that for longer-lived branches, there's a good chance B only got created after you branched off.

So unless you catch up to reality (i.e. sync), you won't even know you should make those changes to B. Hence my post ;)

[ Parent | on HN ]