-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Jan 3, 2009, at 11:54 AM, Ulrich Eckhardt wrote:
1. I think that a patch can not e.g. capture a moved, renamed or
deleted file.
Further, it can not handle e.g. things like the executable bit or
similar
things that SVN otherwise does manage. That is what makes a patch only
partially suitable.
Bazaar bundles handle moved, renamed and deleted files and
directories, afaik. Executable bits and other file metadata are
harder because such properties are OS specific, and Bazaar tries to be
OS agnostic.
2. You don't checkout anew. You simply switch ("svn switch") your
existing
working copy to the branch which just pulls the differences and
merges them
into your existing working copy. Or, you could merge the changes on
a branch
("svn merge") into your working copy.
I know that many VCSs support this style of working, but this just
doesn't fit my brain. I much prefer separate working trees, each with
its own feature or fix.
- -Barry
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
iQCVAwUBSV+ymnEjvBPtnXfVAQIDKgQArzTiPmBZnrVBnfrn4kfIJ/21cT+RVCsI
S9rtIrMRtxAETIeA0ko/9zPLatktYft8hpK77IBo2f1ZSs9vpGRZbm30j4OtQOAR
/A/1hr6yGCNzc0OtbHoB7OoJ+1+0ORv+otmUIXJYWTiIOhG3y6oj1gWYkmwhYJRc
87333i8VIj0=
=azL0
-----END PGP SIGNATURE-----
_______________________________________________
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
