Will re-basing support be added into Bazaar core ?

[Stephen J. Turnbull]

Ben Finney writes:

 > I don't see how that's true. The loom has the crucial difference that
 > none of the existing revisions are altered, nor are their relationships
 > in the history altered.

The same is true of git by construction.  New revisions are added,
with the same semantic content (you hope).  Exactly the same is true
for loom, right down to the "(you hope)".  The only difference is the
UI by which you refer to the new and/or old revisions (ie, how you get
them to manifest in a workspace so you can build and test them), and
how they are represented in the VCS database.  Git doesn't distinguish
between revisions "as they happened" and "as they are rebased".  Loom
does distinguish between "revisions" and "threads".  Purely UI.

 > This seems to be to be the crucial difference between a loom update and
 > a rebase, so I'm still not seeing how you conflate the two ("just as
 > true of looms but worse") in this regard.

Try grokking git instead of accepting the FUD about it.  Think about
how applying a loom patch in a different context is similar to
checkout of a rebased revision (the workspaces will be identical, and
identically untested) but loom provides much more flexible control of
which patches are applied where than rebase does.  (Of course git
rebase --interactive is extremely flexible, but loom provides
additional structure that makes the flexibility more controllable.)

You may learn to hate git like a Martian, but you'll stop fearing it.
You'll also learn a lot about VC.