https://bugzilla.wikimedia.org/show_bug.cgi?id=15308
--- Comment #17 from Roan Kattouw <roan.katt...@gmail.com> 2011-03-14 11:20:07 UTC --- (In reply to comment #16) > Things are somewhat complicated. Several of the above overlap, or are > interdependent, and cannot be tackled one after the other while maintaining > error-free running code at the same time, I am afraid. Committing often would > require a branch which is not neccessarily free of additional, temporary, > issues all the time. If that is what you want, I shall go ahead when I am back > from work. You shouldn't commit one big "this fixes everything" commit, but it's also not always practical to commit separately for every issue when there are dependencies and reorganizations involved. But there's some middle ground there. If you can reasonably split up a commit such that the parts make sense individually and things don't break in between, do so. In practice, this means you should avoid commits that fix two unrelated issues. If you're doing a large-ish reorganization or something, it sometimes makes sense to split it up in multiple commits, leaving things slightly broken in the meantime. This is fine on occasion if the breakage isn't too bad and doesn't stick around for too long. For instance, it's not unusual to rename files in one commit (breaking things) and change some other things in a second commit a few minutes later (fixing things). -- Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
