Is there a process for managing large branch / repository revision history?

Hi Eric,

The repository stores a copy of the history and for a tree this size
that's about a typical size for it.

If you have multiple branches or working trees on one machine, you
don't need a copy of the history. Use 'bzr init-repo' and put the
branches under that, or check out the bzr-colo plugin.

If you're concerned about the size of the repository on the main
location of the trunk branch, then that's about all we can do: half
the size of the tree is already pretty good. 'bzr pack' may make it a
bit smaller.

If you want a checkout with no local history at all, use 'bzr checkout
--lightweight'. This will be slow if the repository is across a slow
network.

hth
Martin

On 13 October 2011 23:30, Eric Risler
<email address hidden> wrote:
> New question #174136 on Bazaar:
> https://answers.launchpad.net/bzr/+question/174136
>
> Hi,
>
> We have a project which the main truck/branch is just over 900mb. When we checkout this branch, the .bzr directory is over 400MB...about 1/2 the branch size.
>
> Is this normal?
> How can we (or just can we?) manage / see the revision history size?
> Is there any way to cut away some of the revision history that we don't think we need?
>
> Thanks.
>
> Bazaar is great. :)
>
> --
> You received this question notification because you are an answer
> contact for Bazaar.
>
>

Okay, so the size of the history is appropriate then. You mention using init-repo for another branch...can you clarify: We have a shared repo (without trees) served up using bzr server over ssh. We have many branches underneath the repo. Is it valid to start a new repo underneath this repo using --inti-repo? or will this cause problems?

Thanks Martin.

On 18 October 2011 01:50, Eric Risler
<email address hidden> wrote:
> Question #174136 on Bazaar changed:
> https://answers.launchpad.net/bzr/+question/174136
>
> Eric Risler posted a new comment:
> Okay, so the size of the history is appropriate then. You mention using
> init-repo for another branch...can you clarify: We have a shared repo
> (without trees) served up using bzr server over ssh. We have many
> branches underneath the repo. Is it valid to start a new repo underneath
> this repo using --inti-repo? or will this cause problems?

If you already have a shared repository on the server there's no
particular need to create a new one. Things may be faster if you make
a repository for each group of related branches, rather than eg having
several different projects all in one repository.

Can you explain your situation more systematically? Is the space a
problem on the server, or somewhere else?