ganieda:/data/tmp% bzr init --rich-root-pack c1
Standalone tree (format: rich-root-pack)
Location:
branch root: c1
ganieda:/data/tmp% bzr init --rich-root-pack c2
Standalone tree (format: rich-root-pack)
Location:
branch root: c2
ganieda:/data/tmp% cd c2
ganieda:/data/tmp/c2% touch a
ganieda:/data/tmp/c2% bzr add; bzr ci -m add\ a
added a
Committing to: /data/tmp/c2/
added a
Committed revision 1.
ganieda:/data/tmp/c2% cd ../c1
ganieda:/data/tmp/c1% bzr branch ../c2
Branched 1 revision(s).
ganieda:/data/tmp/c1% bzr join c2
renamed file:///data/tmp/c1/c2/.bzr to .bzr.retired.0
ganieda:/data/tmp/c1% bzr st
working tree is out of date, run 'bzr update'
renamed:
=> c2
unknown:
c2/.bzr.retired.0/
This is of course not a situation that'll be happening often in real-life. It doesn't happen when c1 is not empty.