On Mon, Mar 7, 2011 at 17:28, Daniel Stutzbach <stutzb...@google.com> wrote:
> With a branch you can easily view the full patch, making a branch strictly > more general. > > The advantage of having a branch comes when you want to review the second > or third iteration of a proposed change. With a branch, you can view the > diff between the latest iteration and the branch point to view the change as > a cohesive whole. Or you can view the diff between the latest iteration and > the last iteration you reviewed, to see if they have addressed your earlier > comments or not. > > You can also just tweak a few things and push the changes back to them. > They can easily merge your changes with any changes they've made in the > meantime (which is hard to do if you're pushing patch files around). > Actually, it isn't. As I said, Rietveld handles this the same way. The fact that it got there by analyzing subsequent patches is really immaterial -- except in so far as it marks the intended changes more clearly. -- Thomas Wouters <tho...@python.org> Hi! I'm a .signature virus! copy me into your .signature file to help me spread!
_______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
