From: "Nikita V. Youshchenko" <yoush@cs.msu.su>
To: git@vger.kernel.org
Subject: local git clone problem
Date: Mon, 30 Jul 2007 12:42:54 +0400 [thread overview]
Message-ID: <200707301242.54669@sercond.localdomain> (raw)
Hello.
I'm trying to clone a local git repository and it fails:
nikita@blacky:~/linux-2.6> git clone -l -s -n . ../new
Initialized empty Git repository in /home/nikita/new/.git/
/usr/bin/git-clone: line 381: cd: /home/nikita/new/.git/refs/remotes/origin: No such file or directory
The command is [almost] from git-clone(1) examples.
Examining .git in the new directory after the error:
nikita@blacky:~/new> ls -aR
.:
./ ../ .git/
./.git:
./ ../ branches/ config description HEAD hooks/ info/ objects/ refs/
./.git/branches:
./ ../
./.git/hooks:
./ applypatch-msg post-commit post-update pre-commit update
../ commit-msg post-receive pre-applypatch pre-rebase
./.git/info:
./ ../ exclude
./.git/objects:
./ ../ info/ pack/
./.git/objects/info:
./ ../ alternates
./.git/objects/pack:
./ ../
./.git/refs:
./ ../ heads/ tags/
./.git/refs/heads:
./ ../
./.git/refs/tags:
... (same as in .git/refs/tags/ of the original directory)
Looks like for some reason, .git/refs/remotes in the new directory is
not created, but referenced.
Original repository was created by 'git init' and then populated with several
'git remote add' and 'git remote update' commands.
This is with debian package git-core 1:1.5.2.1-1~bpo.1 (current debian
etch-backports version)
Is this a bug?
If not, what I'm doing wrong?
Is it possible to manually 'fix' the original directory such that local
clones from it will become possible?
Nikita
reply other threads:[~2007-07-30 9:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200707301242.54669@sercond.localdomain \
--to=yoush@cs.msu.su \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox