Maintaining multi-layered, interdependent branches

[Ben Finney]

Ben Finney <bignose+hates-spam at benfinney.id.au> writes:

> I don't understand what ‘record’ does that isn't already covered by
> ‘commit’.

I've now read the ‘HOWTO’ and ‘README’ in detail, and it's not at all
clear what ‘record’ does as compared to ‘commit’. More to the point,
I don't know when one should use it.

I share the sentiment here:

    As well as committing revisions to individual threads, the “bzr
    record” command can be used to commit the state of the loom as a
    whole. I haven’t really worked out when I should be using the
    command.
    […]
    Despite the quirks in the interface, it does make the relevant
    work flows easier. It will be interesting to see how the plugin
    develops.

    <URL:http://blogs.gnome.org/jamesh/2008/04/01/bzr-loom/>

> Perhaps what is lacking is a clear deliniation of what about the
> user's mental model needs to be changed when going from a non-loom
> branch to a loom.

Hopefully people can explain these things to Karl Fogel, who seems
better at asking questions than I :-)

-- 
 \     Rommel: “Don't move, or I'll turn the key on this can of Spam!” |
  `\                               —The Goon Show, _Rommel's Treasure_ |
_o__)                                                                  |
Ben Finney