On 04/30/2011 04:37 PM, Vincent van Ravesteijn wrote: > >> g) make it easier to review patches (mailing list is a pain) > The problem is not with the mailing list. The problem IMHO is with the > fact that it is difficult to review a patch if it is only a little part > of a much larger patch committed earlier. Or when a feature seemed to > be so complex that its development got scattered into 20 different > patches correcting each other, introducing stuff that might have been > forgotten in other patches, or fixing newly introduced bugs. > I think this sort of thing has been a really serious problem at certain points in the past.
My big problem with svn is this: If you want to develop a new and fairly complicated, you have three choices about where to do it: (1) In trunk; (2) In a private branch; (3) On your local machine, and then you commit when everything is pretty much done. The problem with (3) is that you lose the ability to interact with other developers. The problem with (2) is that svn branches are so difficult to use. The problem with (1) is that you have half-finished features in trunk all the time, and backing them out can be very difficult. Git solves this problem. And, as I said, in a different message, the learning curve is not nearly so bad as people think. Richard
