-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Jul 13, 2007, at 12:24 PM, Facundo Batista wrote:
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?
You can still have a patch methodology if your internet connection really sucks. But if you have good enough access to the current Subversion repository, then you probably have good enough access to use a free branch hosting service like Launchpad. - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) iQCVAwUBRpe3aHEjvBPtnXfVAQL1swQAuXP/QX5c/isttwQ3Et/N7fp6mG9a+sA+ HX7G6rSWxaYGtmYOjXTqjeou/QEoNlEtOqvZQcAJQ4iObMVg0mVIVFxixPln3JPQ u4XNt37FklJh7q0tbvi6VQeBi82beqWuL6+MTE6dMD1ruRAkJ/zpM9/ruiCBSmSB XO84dNkv/dY= =sUf+ -----END PGP SIGNATURE-----