Creating a bzr branch out of a series of tarballs

[Gordon Tyler]

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

On 3/5/2011 8:24 AM, Eli Zaretskii wrote:
> Does this mean that "bzr mv --auto" will also handle removed files, if
> I remove the contents of the working tree before populating it with
> the next version?  The documentation of "bzr mv --auto" seems to talk
> only about renames.

No, but 'bzr rm' on its own without arguments will "scan for files that
are being tracked by Bazaar but missing in your tree and stop tracking
them for you."

It looks like bzr-automv may also handle deletions. But I can't find the
repository for bzr-automv anymore.

> Also, does "bzr mv --auto" make the automv plugin unneeded/obsolete?
> That is, does "bzr mv --auto" do everything automv does?

According to stackoverflow.com:

automv plugin allows you to specify the similarity level between files
with --threshold. Both have --dry-run to check heuristics before record
actual renames. mv --auto is builtin, so you don't need to bother to
install additional plugins, vanilla bzr will be enough. Historically
automv was born first. That's all. – bialix Jan 21 '10

Ciao,
Gordon

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJNcl8IAAoJEIrPJfWinA2uZGQH/1tDcGzR4dTVRz/9pqah+2IF
Dj0xm4kgDVS+tbRVshXSVuLUnLGX7r5HQoMp0EeIsIyulAzbuliQrhQHqpjxYR/u
z6Of6eiFDm2p3ZClVYE4N/oo81w8XvMRuFe1G76ztQiEWv73YUZaiWMjV7TVlGrY
wAnEt2SanSpTPwXYxGa/bP3Cuq9H5WMHQIsFZGKS4kwP4qZ3/ivlMPD1URZPThg3
Lb+BbRNK7Vay4Qocgz6TUk3t32ADpkDvmTUQgteICC+Yyp80LwztmdpUkqtqOdWA
5yPfxGLbrvhCeHYjnweJ6gmB32GJXcb2XrZdHvexW5e7cihUpCCb+7GjbqFZNnM=
=CJIL
-----END PGP SIGNATURE-----