The scary thing in -1.18rc1 is that now, when repeating the bzr commit, it goes as follows:
jal@mabillon:~/nbzr/vp-3.2-hot$ bzr commit -m "-3.2 initial"
bzr: ERROR: Working tree is out of date, please run 'bzr update'.
jal@mabillon:~/nbzr/vp-3.2-hot$ bzr update
All changes applied successfully.
Updated to revision 2.
jal@mabillon:~/nbzr/vp-3.2-hot$ bzr commit -m "-3.2 initial"
Committing to: /home/jal/nbzr/vp-3.2-hot/
aborting commit write group: PointlessCommit(No changes to commit)
bzr: ERROR: No changes to commit. Use --unchanged to commit anyhow.
So even though I got an exception something the commit appearently worked. This differs from the behaviour in 1.17.
The scary thing in -1.18rc1 is that now, when repeating the bzr commit, it goes as follows: ~/nbzr/ vp-3.2- hot$ bzr commit -m "-3.2 initial" ~/nbzr/ vp-3.2- hot$ bzr update ~/nbzr/ vp-3.2- hot$ bzr commit -m "-3.2 initial" nbzr/vp- 3.2-hot/
jal@mabillon:
bzr: ERROR: Working tree is out of date, please run 'bzr update'.
jal@mabillon:
All changes applied successfully.
Updated to revision 2.
jal@mabillon:
Committing to: /home/jal/
aborting commit write group: PointlessCommit(No changes to commit)
bzr: ERROR: No changes to commit. Use --unchanged to commit anyhow.
So even though I got an exception something the commit appearently worked. This differs from the behaviour in 1.17.