On 7/17/07, <b class="gmail_sendername">Robert Collins</b> <<a href="mailto:robertc@robertcollins.net">robertc@robertcollins.net</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Tue, 2007-07-17 at 10:36 +1000, Martin Pool wrote:<br>><br>> testing /home/mbp/bzr/trunk/bzr 0.19dev python-2.5.1 unix<br>> bzrlib /home/.....<br><br>That would be a big improvement.<br><br>-Rob<br></blockquote>
</div><br>another option is to normally only show the reduced version info like robert suggested, <br>but print a WARNING if there the current working directory <br>contains a bzr executable, which is not equal to the one being tested.
<br><br>(this might cause some false warnings if you used symlinks and<br>they are effectively the same, but I don't think thats too bad)<br><br>This sort of thing (testing the wrong bzr) have bitten me so many times that
<br>I now remember most of the time to double check this if something looks fishy.<br>I think this is a regular pitfall for new bzr developers and well worth addressing.<br><br>regards<br>marius<br><br><br><br>