behaviour with manual directory copies?

[Max Bowsher]

On 26/04/11 02:27, ceti_331 wrote:
> 
> Q1:Lets say a user just copies & renames a directory containing a BZR
> branch/repo..
> then starts working in it, committing etc,
> then tries to use bzr commands (push , pull , merge) to move data to & from
> other branches/repos (or vica versa)
> 
> Is there any defined behaviour?
> 
> I've just done a quick experiment and it sort of works so far (i.e. its
> showing up commits in the log as coming from the renamed location).
> But is this going to break with say shared repositories etc.
> 
> Q2:-
> lets say you're doing single-user workflow using USB sticks (no network) to
> copy backups around, and you do the same thing.. (i.e. just copy the
> branch/repo directory to the stick, then copy it on your other machine).
> Is this going to confuse it too.. or are you safely copying a workable
> history around this way.
> 
> are these going to just work, or will the system start spitting out error
> messages figuring out things are changing without you telling it properly..
> 
> I'm asking because I want to know how this will behave if I give it to
> artists who may not be used to such a DVCS/branching system


So long as you don't separate a branch from its repository (e.g. by
copying a branch but not its enclosing shared repository, or by copying
a branch without a branch it is stacked on), copying a branch is mostly
equivalent to 'bzr branch'ing it. (The differences being in that you
copied the branch's config, including memorized parent/push etc.
locations, and you copied the working tree)

Max.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: OpenPGP digital signature
URL: <https://lists.ubuntu.com/archives/bazaar/attachments/20110430/d14fd01d/attachment.pgp>