[11:00] It is possible to fetch remote changes without changing current revision number (like 'git fetch' does)? [11:01] into a repo sure [11:05] Kakadu: bzr fetch-revisions IIRC [11:07] jelmer: no such command on my machine [11:07] Kakadu: you'll need to have bzrtools installed, I think [11:08] installed already [11:11] Kakadu: bzr fetch-ghosts? [11:12] Purpose: Attempt to retrieve ghosts from another branch. [11:12] No idea what 'ghost' means [11:13] * Kakadu is googling [11:13] it's uh complicated [11:13] I think you basically want what I said, ie use a repo and pull into it [11:18] bob2: i.e. I need to make a repo in another place of my filesystem and pull to it? Am I understanding u correctly? [11:25] guess so [11:25] what are you trying to do [11:38] I have a tool which gets sources from many locations [11:39] and we have designed some API which is good for git and darcs [11:39] API is here: https://github.com/samoht/opam/blob/master/src/repositories/opamVCS.mli [11:39] oh man [11:39] And I'm thinking how suitable it will be for bazaar [11:39] bob2: what do you expect? package manager [11:40] afk 5 min [11:41] well, you'll need to read the bzr tutorial then [11:41] so you know what a shared repo is [12:04] That API documentation has a confusing use of the term staging area [12:05] In Git terminology it usually refers to the index; you seem to be using it more in the context of a repository containing changes that are not yet applied to the working tree/index. [12:15] it seems that bzr's shared repo is what git has by default... [12:16] sort of [12:16] you'll need to learn bzr if you want to write a tool on top of it === wedgwood_away is now known as wedgwood === mmrazik is now known as mmrazik|otp === mmrazik|otp is now known as mmrazik === iBasic is now known as BasicOSX === deryck is now known as deryck[lunch] === deryck[lunch] is now known as deryck