No I didn't. I guess it's just bad luck that 541fc218 was committed a
few hours before I reported the issue ;) I generally git-pull in the
morning, so I pulled before that got committed.
Actually, I ran into it last week but forgot to mention it then.
-Kevin
On Jun 5, 2008, at 11:14 PM, Jeff King wrote:
On Thu, Jun 05, 2008 at 04:48:56PM -0700, Kevin Ballard wrote:
The new builtin git-clone is still broken in that it doesn't unpack
the
working tree if the clone happened over http.
Did you try with a git that contains 541fc218?
-Peff
--
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
--
Kevin Ballard
kevin@xxxxxxxxxxx
--
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
