in-line :-

On 9/21/13, Philip Oakley <> wrote:

Dear Philip,
Thank you first of all for taking your time to answer and showing
interest in my query.

> A couple of points.
> To get a complete bundle use the --all option.

use the --all option where ? During the creation of the bundle or
during the unbundling of the bundle ?

Do you mean

:~/games$ git clone flare-game.bundle  --all ?


$ git bundle create flare-game.bundle --all

I am guessing this is the latter one you mean but would be better if
you can be a bit more precise.

> Having only aked for one branch, that was all you got, and it looks like
> it wasn't the current HEAD at the time, so HEAD wasn't included in the
> bundle - hence the warning (but not an error ;-) when you cloned from
> the bundle. (but it still left you without anything checkedout)


> So at that point you have a single branch (in your remotes), no head and
> your remote is the bundle you cloned from, which is what the
> is confirming. So just a little confusion that's all.


> At that point you then do you update your remote config (there are
> command that will set the various remote/config values), and then git
> fetch to get the remainder that you were missing. Then finally you need
> to update your HEAD by checking out a specific branch.

Could you elaborate on the above a bit more, esp. the bit about the
command to set the various remote/config values bit.

> Philip


          Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
065C 6D79 A68C E7EA 52B3  8D70 950D 53FB 729A 8B17

You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
For more options, visit

Reply via email to