checkout in base directory does not honor -r
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Fix Released
|
Undecided
|
Aaron Bentley |
Bug Description
I just tried to find a bug using manual bisect on the history, unfortunately there is still no "bzr update -r REVNO" (like in SVN ;-), so I did a "bzr remove-tree; bzr checkout -r REVNO", but the bug was still there ... after some while I noticed that my checkouts always were the head revision, regardless of the revision number I was giving to checkout. It works if I checkout to another directory, but not within the ?base? directory of a branch ...
This is BZR revision: 2648 of bzr.dev and can be reproduced as follows:
mkdir test
cd test
bzr init
echo a >> s
bzr add s
bzr commit -m a
echo b >> s
bzr commit -m b
bzr remove-tree
bzr checkout -r 1
echo "s is wrong now, it is rev 2 instead of 1!"
cat s
bzr checkout -r 1 . good
echo "good/s is correct, it is rev 1"
cat good/s
Changed in bzr: | |
assignee: | nobody → aaron-bentley |
status: | New → Fix Released |
Found a typo while reading the docs on checkout ...
=== modified file 'bzrlib/ help_topics. py' help_topics. py 2007-07-12 12:07:13 +0000 help_topics. py 2007-07-23 11:55:57 +0000
--- bzrlib/
+++ bzrlib/
@@ -248,7 +248,7 @@
that modify the revision history (as only one copy branch needs to be updated).
Heavyweight checkouts will generally be faster for any command that uses the
history but does not change it, but if the master branch is on the same disk
-then there wont be a noticeable difference.
+then there won't be a noticeable difference.
Another possible use for a checkout is to use it with a treeless repository
containing your branches, where you maintain only one working tree by