When does remove implies removal of parents and siblings?
I'm using the most recent stable Windows build:
C:\MyRepo\
Bazaar (bzr) 2.5.1
Python interpreter: C:\Program Files (x86)\Bazaar\
Python standard library: C:\Program Files (x86)\Bazaar\
Platform: Windows-
bzrlib: C:\Program Files (x86)\Bazaar\
Bazaar configuration: C:/Users/
Bazaar log file: C:\Users\
Compare this interaction:
C:\
unknown:
File.txt
Pippo.txt
a/
C:\
adding a
adding a/Pluto.txt
adding a/Topolino.txt
C:\
removed a/Pluto.txt
Against this one:
C:\
unknown:
File.txt
Pippo.txt
a/
C:\
adding a
adding a/Pluto.txt
adding a/Topolino.txt
C:\
removed a/Topolino.txt
removed a/Pluto.txt
removed a
The only difference is the inclusion of option "--new" in the second one. The effect of "--new" is that also the siblings and parents of "Pluto.txt" are unversioned.
Consider also this example, in which also siblings of directory "a" are added:
C:\
unknown:
File.txt
Pippo.txt
a/
C:\
adding File.txt
adding Pippo.txt
adding a
adding a/Pluto.txt
adding a/Topolino.txt
C:\
removed a/Topolino.txt
removed a/Pluto.txt
removed a
Again, "remove" with "--new" unversions the entire "a" directory, but not its siblings "File.txt" and "Pippo.txt" (showing that the "remove" command is still operating on "a" but it is unversioning too much).
Why Bazaar is behaving like this? Am I missing something?
*** EDIT May 11, 2014 ***
Also the following version is affected:
Bazaar (bzr) 2.6b1
Python interpreter: C:\Program Files\Bazaar\
Python standard library: C:\Program Files\Bazaar\
Platform: Windows-
bzrlib: C:\Program Files\Bazaar\
Bazaar configuration: C:/Users/
Bazaar log file: C:\Users\
Question information
- Language:
- English Edit question
- Status:
- Expired
- For:
- Bazaar Edit question
- Assignee:
- No assignee Edit question
- Last query:
- Last reply: