| 2014-05-11 09:43:41 |
Dario D'Amico |
description |
Most recent stable windows build:
Bazaar (bzr) 2.5.1
Python interpreter: C:\Program Files\Bazaar\python26.dll 2.6.6
Python standard library: C:\Program Files\Bazaar\lib\library.zip
Platform: Windows-7-6.1.7601-SP1
bzrlib: C:\Program Files\Bazaar\lib\library.zip\bzrlib
Bazaar configuration: C:/Users/Dario/AppData/Roaming/bazaar/2.0
Bazaar log file: C:\Users\Dario\Documents\.bzr.log
There is a branch with a file and a directory. The directory contains two more files.
=== INTERACTION 1 ===
C:\repo\trunk>bzr stat
unknown:
a/
z.txt
C:\repo\trunk>bzr add
adding a
adding z.txt
adding a/x.txt
adding a/y.txt
C:\repo\trunk>bzr remove a/x.txt --new
removed a/y.txt (but kept a copy: a/y.txt.~1~)
removed a/x.txt (but kept a copy: a/x.txt.~1~)
removed a (but kept a copy: a.~1~)
It is not clear how the filename is used with the --new option. Compare the above
interaction with the following, in which no filename is specified and --new is used:
=== INTERACTION 2 ===
C:\repo\trunk>bzr stat
unknown:
a/
z.txt
C:\repo\trunk>bzr add
adding a
adding z.txt
adding a/x.txt
adding a/y.txt
C:\repo\trunk>bzr remove --new
removed z.txt (but kept a copy: z.txt.~1~)
removed a/y.txt (but kept a copy: a/y.txt.~1~)
removed a/x.txt (but kept a copy: a/x.txt.~1~)
removed a (but kept a copy: a.~1~)
Finally, consider the case in which the --new option is not specified:
=== INTERACTION 3 ===
C:\repo\trunk>bzr stat
unknown:
a/
z.txt
C:\repo\trunk>bzr add
adding a
adding z.txt
adding a/x.txt
adding a/y.txt
C:\repo\trunk>bzr remove a/x.txt
removed a/x.txt (but kept a copy: a/x.txt.~1~)
I feel like interactions 2 and 3 shows the expected behavior as
described in the manual, while interaction 1 shows an undocumented
(and at least to me counterintuitive) behavior and looks like a bug. |
Most recent stable windows build:
Bazaar (bzr) 2.5.1
Python interpreter: C:\Program Files\Bazaar\python26.dll 2.6.6
Python standard library: C:\Program Files\Bazaar\lib\library.zip
Platform: Windows-7-6.1.7601-SP1
bzrlib: C:\Program Files\Bazaar\lib\library.zip\bzrlib
Bazaar configuration: C:/Users/Dario/AppData/Roaming/bazaar/2.0
Bazaar log file: C:\Users\Dario\Documents\.bzr.log
There is a branch with a file and a directory. The directory contains two more files.
=== INTERACTION 1 ===
C:\repo\trunk>bzr stat
unknown:
a/
z.txt
C:\repo\trunk>bzr add
adding a
adding z.txt
adding a/x.txt
adding a/y.txt
C:\repo\trunk>bzr remove a/x.txt --new
removed a/y.txt (but kept a copy: a/y.txt.~1~)
removed a/x.txt (but kept a copy: a/x.txt.~1~)
removed a (but kept a copy: a.~1~)
It is not clear how the filename is used with the --new option.
Compare the above interaction with the following, in which no
filename is specified and --new is used:
=== INTERACTION 2 ===
C:\repo\trunk>bzr stat
unknown:
a/
z.txt
C:\repo\trunk>bzr add
adding a
adding z.txt
adding a/x.txt
adding a/y.txt
C:\repo\trunk>bzr remove --new
removed z.txt (but kept a copy: z.txt.~1~)
removed a/y.txt (but kept a copy: a/y.txt.~1~)
removed a/x.txt (but kept a copy: a/x.txt.~1~)
removed a (but kept a copy: a.~1~)
Finally, consider the case in which the --new option is not
specified, but filename is given:
=== INTERACTION 3 ===
C:\repo\trunk>bzr stat
unknown:
a/
z.txt
C:\repo\trunk>bzr add
adding a
adding z.txt
adding a/x.txt
adding a/y.txt
C:\repo\trunk>bzr remove a/x.txt
removed a/x.txt (but kept a copy: a/x.txt.~1~)
I feel like interactions 2 and 3 shows the expected behavior as
described in the manual, while interaction 1 shows an undocumented
(and at least to me counterintuitive) behavior and looks like a bug. |
|
