Il giorno mar, 28/01/2014 alle 15.03 -0800, Kevin DuBois ha scritto: > I think we have 3 issues that drive up diff size:
> 1) Bzr has branches, but they aren't cheap enough. The simple fact > that you have to compile each branch in its own directory is too big > of a cost to branch as often as I would in git. Well, that's not completely true. I mean, a part that having ccache can help even using different folders, but you can setup bzr using the lightweight checkout mode that allows you to use just one single work folder for the working branch, while easily switching between branches that are, only logically, in different folders. So at the end I've: unity ├── BRANCHES │ ├── 5.0 │ ├── 7.1 │ ├── ... │ └── feature-1-branch ├── workdir │ ├── build │ ├── cmake │ ├── dash │ └── ... Where all my work is done only in work dir, and I can use bzr switch to move to a different branch that I might create or fetch in BRANCHES. See [1] for more hints, but that definitely made my workflow with bzr much more productive (so, that switching branch and recompiling only rebuilds what has changed). Ah, also with using the bzr q* tools, where especially qdiff is a must. [1] https://www.taoeffect.com/blog/2009/06/using-bazaar-like-git-repoalias-plugin/ -- Mir-devel mailing list Mir-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/mir-devel
