3 ms·

Furthermore, he's probably confusing mercurial with something that don't even exist bazaar expects you to have a separate working copy (directory) for each bra

Furthermore, he's probably confusing mercurial with something that don't even exist bazaar expects you to have a separate working copy (directory) for each branch, but you can have multiple branches stored in the same repository without any problem (I just wished that git people actually knew how do other tools work... but, alas! Now it's too late for underdogs like bazaar or darcs to catch up)

JoshTriplett 13y ago
> bazaar expects you to have a separate working copy (directory) for each branch, but you can have multiple branches stored in the same repository without any problem Those are functionally equivalent, in that they both mean branching is not instantaneous.
- rbehrends 13y ago
  Those are functionally equivalent, in that they both mean branching is not instantaneous. They are not functionally equivalent. A "bzr branch" with a shared repository will only populate the working tree and does not have to duplicate the repository. It is functionally closer to "git-new-workdir" than "git clone" or "git branch". To have instant branching in Bazaar, you can use co-located branches. Branches with their own directories exist for the use case where the accumulated cost for rebuilds after branch switches is more costly than populating a new directory with a checkout or if you need two checkouts in parallel. They also exist in Bazaar for simulating a workflow with a central server and no local repository data.
masklinn 13y ago
> bazaar expects you to have a separate working copy (directory) for each branch, but you can have multiple branches stored in the same repository without any problem Shared repositories didn't originally exist and IIRC were added to avoid data duplication. Furthermore, they don't fix the multiple working copies problem (you have to use lightweight checkouts or collocated branches for that).

JoshTriplett 13y ago

> bazaar expects you to have a separate working copy (directory) for each branch, but you can have multiple branches stored in the same repository without any problem Those are functionally equivalent, in that they both mean branching is not instantaneous.

rbehrends 13y ago
Those are functionally equivalent, in that they both mean branching is not instantaneous. They are not functionally equivalent. A "bzr branch" with a shared repository will only populate the working tree and does not have to duplicate the repository. It is functionally closer to "git-new-workdir" than "git clone" or "git branch". To have instant branching in Bazaar, you can use co-located branches. Branches with their own directories exist for the use case where the accumulated cost for rebuilds after branch switches is more costly than populating a new directory with a checkout or if you need two checkouts in parallel. They also exist in Bazaar for simulating a workflow with a central server and no local repository data.

masklinn 13y ago

> bazaar expects you to have a separate working copy (directory) for each branch, but you can have multiple branches stored in the same repository without any problem Shared repositories didn't originally exist and IIRC were added to avoid data duplication. Furthermore, they don't fix the multiple working copies problem (you have to use lightweight checkouts or collocated branches for that).