Il giorno mar, 28/01/2014 alle 14.47 +0800, Daniel van Vugt ha scritto:
>1. Create a diff: bzr diff --old :parent > ~/bigone.diff
>2. Create a new branch and reapply the changes: patch -p0 <
> ~/bigone.diff
>3. Identify changes to drop: bzr status or bzr diff
>4. Drop them: bzr re
On Tue, 2014-01-28 at 12:32 +0100, Marco Trevisan wrote:
> Il giorno mar, 28/01/2014 alle 14.47 +0800, Daniel van Vugt ha scritto:
> >1. Create a diff: bzr diff --old :parent > ~/bigone.diff
> >2. Create a new branch and reapply the changes: patch -p0 <
> > ~/bigone.diff
> >3. Identif
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. Furthermore, as illustrated by the
conversation above, if you wa
