[Python-Dev] Subversion branch merging
Barry Warsaw
barry at python.org
Fri Jul 13 18:10:55 CEST 2007
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Jul 13, 2007, at 11:39 AM, skip at pobox.com wrote:
> Barry> diffs are so 20th century. :)
>
> How do you compare two versions of something without some sort of
> diff?
Well okay, you caught me being flippant. :)
Sure, you visually compare with diffs, but you apply those changes
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.
- -Barry
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
iQCVAwUBRpekD3EjvBPtnXfVAQLBqwP/RbJ3VhArWjijJ99/u3CzAy0xbcvnUIEv
htlZ/2PBXGZ+ZZm0uQiQcnwlczVUVAiyopdPgTAUmerh9aYWZTP8rtC3SIG7gBDz
6QdNYMl2Rvh5AsvLNXo3HzTyVx74cKHEy91csUuoUWomBa1dR9DVRsT+CpbwM4U8
q11cm7kjXa4=
=v4w0
-----END PGP SIGNATURE-----
More information about the Python-Dev
mailing list