Since we kinda get this a lot, I added it to the FAQ<br><a href="http://bazaar-vcs.org/FAQ#head-927e36ce76d7ee3a9ef59baaf6aa839fc46c36aa">http://bazaar-vcs.org/FAQ#head-927e36ce76d7ee3a9ef59baaf6aa839fc46c36aa</a><br><br>it is probably complete, so please update it if you have better insight on this matter.
<br><br><div><span class="gmail_quote">On 8/14/07, <b class="gmail_sendername">Martin Pool</b> <<a href="mailto:mbp@sourcefrog.net">mbp@sourcefrog.net</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 8/14/07, Hendy Irawan <<a href="mailto:gauldong@gmail.com">gauldong@gmail.com</a>> wrote:<br>> What does bazaar mean by:<br>><br>> ceefour@ojalanow:/media/prestige/home/ceefour/project/layout_mania/src$<br>
> bzr push svn+http://tools.assembla.com/svn/layout_mania<br>> This transport does not update the working tree of:<br>> svn+http://tools.assembla.com/svn/layout_mania<br><br>In Bazaar, branches are commonly colocated with working trees. By
<br>contrast in Subversion the branch is inside the repository, and always<br>in a different directory from the working tree.<br><br>For some Bazaar transports like ftp and sftp, if there is a remote<br>working tree then we can't update it. (This is partly because of
<br>limits in what we can do over the transport and partly that we just<br>don't support it.)<br><br>But for an svn branch there probably is no tree there, so this message<br>seems to be emitted when it should not be.
<br><br><br>--<br>Martin<br><br></blockquote></div><br><br clear="all"><br>-- <br><a href="http://bazaar-vcs.org">bazaar-vcs.org</a><br>Because I don't trust Version Control Systems with less than 6953 unit tests.