On 2010-07-28, at 11:27 AM, Andreia Vidigal Gaita wrote: > > Dropping the per-file changes as a rule is not good, I think. Things > won't be as well documented as they should be, and we'll end up having > to dig through the commit itself to parse the code and try to understand > which change does what. I'm all for detailed commit messages that give > us as much information as possible. >
I'm not so sure I agree here, our commits by and large tend to be pretty atomic. Thats not to say that it cannot have unintended consequences, but you're going to need to understand the motivation behind the entire commit to fix an unintended consequence regardless to ensure that you dont go and break whatever the fix was for. -g
_______________________________________________ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
