On Thu, 03 May 2012 16:09:15 -0000, Michael Witten wrote:
On Thu, 03 May 2012 14:23:59 +0200, Hallvard Furuseth wrote:
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.
Yes, I know. I just don't know why.
--
Hallvard
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html