git clone broken in next
- Date: Wed, 14 May 2008 23:54:39 -0400
- From: Kevin Ballard <kevin@xxxxxx>
- Subject: git clone broken in next
Something's horribly wrong in next. I just installed the latest from next and then ran
git clone git://github.com/kballard/github-gem.gitThe resulting repo had absolutely nothing in the workdir. `git status` claims every single file is deleted but not updated. `git checkout -f HEAD` fixed the workdir.
This is 100% repeatable with different repositories. $ git --version git version 1.5.5.1.373.gce4aa (this is the tip of next plus a single documentation patch).Oddly, all of the tests with "clone" in their name seem to be passing just fine.
Ok, after running a git-bisect, I narrowed it down to 8434c2f1afedb936e0ea8c07ce25733013c2f743 (Build in clone).
My system is Mac OS X 10.5.2. -- Kevin Ballard http://kevin.sb.org kevin@xxxxxx http://www.tildesoft.com -- 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
- Follow-Ups:
- Re: git clone broken in next
- From: Jeff King
- Re: git clone broken in next
- Prev by Date: Re: [PATCH 1/2 v2] cvsexportcommit: chomp only removes trailing whitespace
- Next by Date: Re: What's cooking in git.git (topics)
- Previous by thread: [PATCH] Documentation/git-filter-branch: Fix word usage for --commit-filter
- Next by thread: Re: git clone broken in next
- Index(es):