On Tue, 19 Sep 2006, Petr Baudis wrote: > > Current git#next is totally broken wrt. cloning over HTTP, generating refs > at random directories. Of course it's caused by the static get_pathname() > buffer. lock_ref_sha1() stores return value of mkpath()'s get_pathname() > call, then calls lock_ref_sha1_basic() which calls git_path(ref) which > calls get_pathname() at that point returning pointer to the same buffer. Hmm. This was exactly the schenario why I did commit e7676d2f6454c9c99e600ee2ce3c7205a9fcfb5f - allowing a couple of overlapping paths Isn't that in the "next" branch too? Of course, that still assumes that you strdup() the result at _some_ time, and can't just save it away, but lock_ref_sha1_basic() should do that. Linus - 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