[ANNOUNCE] bzrtools-54 [PATCH] allow tracking a baz project

[Aaron Bentley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

John A Meinel wrote:
| Since you did all of the nice work to make this use a nice revision ID,
| I figured I'd create a patch which allows you to run baz2bzr a second
| time to update it from an earlier revision.

Thanks, John!

| It basically just works by reading the output directory and determining
| what the latest patch is. Then it truncates the ancestry at that point.

I'm inclined to do it slightly differently.  I'd rather not use the
output directory.  The user may have changed it, so that it no longer
reflects the latest revision.  That would falsify the import
information.  And if the update goes wrong, it could leave the output
directory in a bad state.  So I'm planning to:

1. Use the temp dir, but copy the .bzr from the output dir, instead of
initializing the branch
2. Import every revision
3. Instead of renaming the temp dir to the output dir, replace the
output dir's .bzr and do a merge.

That would also make it safe to delete {arch} and all the other
unversioned files, again.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCoFa90F+nu1YWqI0RAqjiAJ9eqnOL8qZsNc1uvc02SrStNqlpewCcC0hC
MtKCQuNxYtCiCiEx/dkkvY0=
=LQiR
-----END PGP SIGNATURE-----