2007/7/13, Barry Warsaw
with merges. This means the end of posting patches because instead what you would do is post the url to a branch that you published some place. It means that branch can be kept up-to-date as its parent branch changes, so a new feature candidate need never get stale. It also means your new feature candidate is a first class revision control branch, just as usable as the trunk, say. So it's much more powerful than trading patch files around.
More powerful, maybe, but also more limitating. Do you still have the "patch" metodologie? How can you provide a patch if you don't have a place to publish the change? 3rd-world--ly yours, -- . Facundo Blog: http://www.taniquetil.com.ar/plog/ PyAr: http://www.python.org/ar/