found 399041 1:1.6.2-1 thanks Hi,
Some notes: 1. "git svn init" from a .git directory still creates .git/.git instead of acting like "git --bare svn init". 2. Similarly for "git init". 3. "git ls-remote .git", "git clone .git", etc. are still unhelpful, so bare repositories with .git subdir are still unusable. 4. In git 1.5.0-rc0 (commit ef0a89a "Provide more meaningful output from 'git init-db'."), git init and git svn init learned to tell what GIT_DIR they are using, so problems 1 and 2 above are harmless now. 5. In git 1.5.0-rc4 the gitk issue was fixed by using the more robust 'show-ref' command (commit 0f57a3 "gitk: Use show-ref instead of ls-remote"). Making a .git/.git directory by accident is difficult, but if you do it, you won't know until you try to use your .git directory as a remote repo. Most git commands (like git show-ref) use setup_git_directory_gently, so they test .git, .git/, ./, etc in turn for objects/, refs/, or valid HEAD. But upload-pack uses enter_repo. So: we should either change upload-pack to not bail out on the first non-git directory it finds, or factor out a better helper function from setup_git_directory_gently. enter_repo repeats the logic from is_git_directory already. But I could be speaking total nonsense --- it's hard to tell at this hour. Hope I haven't wasted too much time with my speculation -- I better sleep before I look into this further. Regards, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
