Re: Newbie grief

[Michael Witten <mfwitten@gmail.com>]

On Thu, 03 May 2012 14:23:59 +0200, Hallvard Furuseth wrote:

> On Wed, 02 May 2012 15:21:29 -0000, Michael Witten wrote:
>
>>On Wed, 02 May 2012 16:21:07 +0200, Hallvard Breien Furuseth wrote:
>>> And in a bare repository:
>>>
>>>     git init --bare foo.git
>>>     cd              foo.git
>>>     git remote add bar ../bar.git
>>>     git fetch      bar
>>>         --> adds bar/master etc.
>>>
>>> For some reason, 'git clone --bare' does not treat the cloned
>>> repository the same way - it just copies it under refs/heads/
>>> instead of refs/remotes/, without even adding it as a remote.
>>
>> What do you mean?
>
> I mean 'git clone --bare bar.git foo.git' does not give foo.git
> a remote named 'origin' with a branch origin/master.  Not sure
> if there is a _simple_ way to do it well either.  init + fetch
> above does not try to hardlink objects/packs like clone does.
>
>> (...)
>>   $ git init bar.git; cd bar.git
>>   $ echo a > a; git add a; git commit -m a; cd ..
>>   $ git clone --bare bar.git foo.git; cd foo.git
>
>    $ git branch -a
>    * master

>From `git help clone':

  --bare
      Make a bare GIT repository. That is, instead of creating
      <directory> and placing the administrative files in
      <directory>/.git, make the <directory> itself the $GIT_DIR.
      This obviously implies the -n because there is nowhere to
      check out the working tree. Also the branch heads at the
      remote are copied directly to corresponding local branch
      heads, without mapping them to refs/remotes/origin/. When
      this option is used, neither remote-tracking branches nor the
      related configuration variables are created.

namely:

                                  Also the branch heads at the
      remote are copied directly to corresponding local branch
      heads, without mapping them to refs/remotes/origin/. When
      this option is used, neither remote-tracking branches nor the
      related configuration variables are created.