Creating a bzr branch out of a series of tarballs

[Aaron Bentley]

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

On 11-03-05 01:13 PM, Eli Zaretskii wrote:
>> Date: Sat, 05 Mar 2011 12:36:00 -0500
>> From: Gordon Tyler <gordon at doxxx.net>
>> CC: bazaar at lists.canonical.com
>>
>>> Well, it looks like automv is still needed.  In my case,
>>> "bzr mv --auto --dry-run" says
>>>
>>>   lib => m4
>>>   lib/rx.c => m4/Makefile.in
>>>   lib/rx.h => m4/gettext.m4
>>>
>>> which is, of course, nonsense: the m4 directory and all of its files
>>> are new, and Makefile.in cannot be possibly similar to rx.c.
>>
>> I don't know how 'bzr mv --auto' matches the files up. Badly, it would seem.
> 
> Yes, it looks like it's too lax in judging similarity.

I'm sorry it's not working for you, but I did a lot of testing on this
with the Launchpad tree (~9000 files), and stronger similarity
requirements prevented files from matching correctly.

I'd be interested to see the contents of rx.c and Makefile.in.  It may
be that they are empty, or nearly so.

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

iEYEARECAAYFAk11EmkACgkQ0F+nu1YWqI0JqQCfbJHl/xA9eLLqjyZ8Z1kjohOn
WUYAn1E9ETgV8Gg2zYEVwXSuLyVJcEuW
=wyMa
-----END PGP SIGNATURE-----