[BUG] Git looks for repository in wrong directory

From: David ‘Bombe’ Roden <hidden>
Date: 2016-06-15 22:44:53

Hi.

The following sequence:

mkdir r1
cd r1
git init
echo a > a
git add a
git commit -m "a"
cd ..
git clone r1 r1.git
cd r1
echo b > b
git add b
git commit -m "b"
cd ..
git ls-remote r1
git ls-remote r1/.

shows that Git searches for a repository in the wrong place. I think the last 
two commands should output exactly the same but "git ls-remote r1" actually 
lists the contents of "r1.git". Is that a bug or is this (extremely 
confusing) behaviour intended?

This also afflicts the behaviour of "git-pull" and friends. I cloned a 
directory and tried to pull new commits but I repeatedly got stuck with an 
older commit. I have to move a second directory that was named like the first 
directory, only with an appended ".git", out of the way so that I could 
access the repository I asked for.

Used Git version is 1.5.6.1 on Linux 2.6.25.6 (Gentoo/x86).


	David

Attachments

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help