Bazaar Git Plugin

After "bzr git-import", then what?

Asked by Eli Zaretskii

After "bzr git-import" finishes (with the gawk repo in this case), I have this directory structure:

gawk.git
 HEAD/
 refs/
  heads/
   gawk-2.10-from-net/
   gawk-stable/
   master/

None of these have working trees. "bzr checkout" in, e.g., HEAD/ or refs/heads/master/ creates a working tree.

Is git-import supposed to leave the branches tree-less, or did I do something wrong?

Question information

Language:
English Edit question
Status:
Solved
For:
Bazaar Git Plugin Edit question
Assignee:
No assignee Edit question
Solved by:
Jelmer Vernooij
Solved:
Last query:
Last reply:
Revision history for this message
Best Jelmer Vernooij (jelmer) said : 		#1

On Sat, 2011-03-12 at 18:39 +0000, Eli Zaretskii wrote:
> New question #148828 on Bazaar Git Plugin:
> https://answers.launchpad.net/bzr-git/+question/148828
>
> After "bzr git-import" finishes (with the gawk repo in this case), I have this directory structure:
>
> gawk.git
> HEAD/
> refs/
> heads/
> gawk-2.10-from-net/
> gawk-stable/
> master/
>
> None of these have working trees. "bzr checkout" in, e.g., HEAD/ or refs/heads/master/ creates a working tree.
>
> Is git-import supposed to leave the branches tree-less, or did I do something wrong?
 Yes - current git-import in trunk mentions this.

We intentionally don't create working tree for each branch as it can
take up a significant amount of disk space if there are a lot of
branches.

Cheers,

Jelmer

Revision history for this message
Eli Zaretskii (eliz) said : 		#2

Thanks Jelmer Vernooij, that solved my question.