Shared repo setup

[mark grandi]

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'

-----Original Message-----
From: "Lucio Crusca" <lucio at sulweb.org>
Sent: ‎7/‎2/‎2014 11:06 AM
To: "Joshua Judson Rosen" <jrosen at harvestai.com>
Cc: "bazaar at lists.canonical.com" <bazaar at lists.canonical.com>
Subject: Re: Shared repo setup

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?


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/bazaar/attachments/20140702/4e571cc2/attachment.html>