Bug in 'bzr mv' patterns on Windows ?

[Maritza Mendez]

Using bzr 1.18...

The behavior of 'bzr mv' with wildcards is different on Windows than on
Linux.

On linux this example works as expected:

martitza at mariposa$ mkdir t
martitza at mariposa$ cd t
martitza at mariposa/t$ bzr init
Created a standalone tree (format:
pack-0.92)
martitza at mariposa/t$ touch cat.txt
martitza at mariposa/t$ touch dog.txt
martitza at mariposa/t$ mkdir pets
martitza at mariposa/t$ bzr add *.txt
adding cat.txt
adding dog.txt
martitza at mariposa/t$ bzr add pets
adding pets
martitza at mariposa/t$ bzr mv *.txt ./pets
cat.txt => pets/cat.txt
dog.txt => pets/dog.txt


But on Windows XP something unfriendly happens:

C:\>mkdir t
C:\>cd t
C:\t>bzr init
Created a standalone tree (format: pack-0.92)
C:\t>echo > cat.txt
C:\t>echo > dog.txt
C:\t>mkdir pets
C:\t>bzr add *.txt
adding cat.txt
adding dog.txt
C:\t>bzr add pets
adding pets
C:\t>bzr mv *.txt .\pets
bzr: ERROR: Could not move *.txt => pets: *.txt is not versioned.

You see that 'bzr mv' seems to have a problem with the wildcard.
Notice that above 'bzr add' did not have a problem with wildcard.

C:\t>bzr mv cat.txt .\pets
cat.txt => pets/cat.txt
C:\t>bzr mv dog.txt .\pets
dog.txt => pets/dog.txt

Imagine having 100 files to move.  The user has to choose between either
'bzr mv' 100 times which preserves history or deleting and readding which
destroys history but works with wildcarding.

Am I missing something, or should I file a bug?  I suppose those are not
mutually exclusive.  :)

Thanks,
~M
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/bazaar/attachments/20090906/746767e2/attachment-0002.htm