[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: bzr repository ready?

From: Eli Zaretskii
Subject: Re: bzr repository ready?
Date: Tue, 24 Nov 2009 06:04:39 -0500

> From: "Stephen J. Turnbull" <address@hidden>
> Cc: address@hidden,
>     address@hidden
> Date: Tue, 24 Nov 2009 18:35:10 +0900
> Eli Zaretskii writes:
>  > I'm not sure I understand this.  With the commands described on the
>  > wiki, my understanding is that the history is in the `trunk' branch,
>  > which is a mirror of (some) branches in the master repository, while
>  > the source tree is in the development branches.  Is that true?
> No.  The history of the project is not just the names, dates, and log
> messages for versions.  It also includes the contents of the files that
> make up each version, either as a copy of the file, or as a sequence
> of diffs against some base version.

Got it, thanks.

>  >   Bazaar allows all the branches in the repository to share storage,
>  >   which makes the branches much more lightweight than CVS branches.
>  >   However, it still takes time to checkout the source tree for each
>  >   branch, and bootstrapping a new tree is annoyingly long.  That is
>  >   why we recommend that for small changes you keep reusing the same
>  >   ``quickfixes'' branch.  This way, once you bootstrapped the
>  >   ``quickfixes'' branch once, the subsequent update, build, and commit
>  >   steps of the update-edit-build-test-commit cycle will all be very
>  >   fast, as long as you continue working in the same branch.
> That's better than what I had.

So where did the part about no build products in the tree fit in here?
Which tree were you talking about?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]