bzr overview questions.

[Rob Browning]

After reading the material on the current bazaar-ng web pages, I had a
few questions.  Some of the answers are implied to greater or lesser
degrees by the existing texts, but I thought the issues might be worth
addressing more directly, presuming they aren't already elsewhere.

  - Is the working directory the same thing as an archive?  i.e. is a
    working directory roughly equivalent to an archive and/or a branch
    in other systems?  This seems to be the case, but it might be
    worth stating clearly.

  - What is the normal way to work with other people using bzr?  The
    main page says:

      * Offers a choice between centralized and decentralized work
        within a single project: when in the office, you can work on a
        shared central branch. For experimental changes or offline
        work you can make a branch on your laptop and merge back in
        later.

    But what does this mean?  Can multiple people commit to the same
    physical destination via sftp (or similar)?

    To put it another way, how does the "in the office" situation
    differ from the laptop situation?

  - Does bzr handle tags, and if so, what is the current recommended
    approach -- to just use multiple branches?  (If so, does bzr use
    hard-links for local branches, or does this require O(n) storage
    for n branches?  I saw the FAQ comment about "cp -al"; does bzr
    itself do the same thing?)

  - Is rsync the recommended way to publish an archive, and if so, are
    there any important considerations?  i.e. What happens if a pull
    is attempted during a sync?

  - Is bzr sensitive to the archive location, i.e. if I move an
    archive, do people pulling just need to know the new location, or
    is their branch going to be confused by the change?

Thanks

-- 
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592  F9A0 25C8 D377 8C7E 73A4