<HTML><HEAD> <META content="text/html; charset=utf-8" http-equiv=Content-Type></HEAD> <BODY> <DIV> <DIV style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri,sans-serif">A shared repo and a standalone branch (a repository that is basically used by only one branch) are more or less the same thing, except a shared repo allows you to share commits, so if you have a project with lots of branches , rather then duplicating all the commits that are in common, it shares them. If you create a shared repo, you need to create a branch inside of it for it to work The warning about the tree not being updated is just because on servers it seems to default to a 'no trees' branch/repo, because since its on a server you really are not interested in the files themselves, just the history. So if you look in the folder structure, you will just find SomeBranchHere/.bzr . To actually get the file contents, you use 'bzr checkout'</DIV></DIV> <DIV dir=ltr> <HR> From: <A href="mailto:lucio@sulweb.org">Lucio Crusca</A> Sent: ‎7/‎2/‎2014 11:06 AM To: <A href="mailto:jrosen@harvestai.com">Joshua Judson Rosen</A> Cc: <A href="mailto:bazaar@lists.canonical.com">bazaar@lists.canonical.com</A> Subject: Re: Shared repo setup </DIV>Thanks for the replies. Now another question arises: Do I really need "bzr init-repo" on the server? Can't I just "bzr init" as if it were a local repo and forget about creating the branch on the server? What do I miss if I do so, apart from the warning about working tree not being updated? </BODY></HTML>