# git-clone still broken wrt. unpacking working tree with http transport 4 messages from 2008-06-05 to 2008-06-06. Participants: Kevin Ballard, Jeff King, Junio C Hamano. Thread: https://gitlist.dev/t/13822 ## Kevin Ballard, 2008-06-05 23:48 Subject: git-clone still broken wrt. unpacking working tree with http transport Message-ID: <0F5C1FC7-258E-44A4-9FE6-AB6696D0B5BE@rapleaf.com> URL: https://gitlist.dev/e/0F5C1FC7-258E-44A4-9FE6-AB6696D0B5BE%40rapleaf.com ``` The new builtin git-clone is still broken in that it doesn't unpack the working tree if the clone happened over http. To test, just go ahead and clone . -Kevin Ballard -- Kevin Ballard kevin@rapleaf.com ``` ## Jeff King, 2008-06-06 06:14 Subject: Re: git-clone still broken wrt. unpacking working tree with http transport Message-ID: <20080606061428.GF18257@sigill.intra.peff.net> URL: https://gitlist.dev/e/20080606061428.GF18257%40sigill.intra.peff.net In-Reply-To: <0F5C1FC7-258E-44A4-9FE6-AB6696D0B5BE@rapleaf.com> ``` 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 ``` ## Kevin Ballard, 2008-06-06 23:28 Subject: Re: git-clone still broken wrt. unpacking working tree with http transport Message-ID: <32A340A4-BB0C-4D0E-9B8D-A4FCEA4B24D1@rapleaf.com> URL: https://gitlist.dev/e/32A340A4-BB0C-4D0E-9B8D-A4FCEA4B24D1%40rapleaf.com In-Reply-To: <20080606061428.GF18257@sigill.intra.peff.net> ``` 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@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -- Kevin Ballard kevin@rapleaf.com ``` ## Junio C Hamano, 2008-06-06 23:30 Subject: Re: git-clone still broken wrt. unpacking working tree with http transport Message-ID: <7vve0mqgz9.fsf@gitster.siamese.dyndns.org> URL: https://gitlist.dev/e/7vve0mqgz9.fsf%40gitster.siamese.dyndns.org In-Reply-To: <32A340A4-BB0C-4D0E-9B8D-A4FCEA4B24D1@rapleaf.com> ``` Kevin Ballard writes: > 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. That's Ok. I tried this locally and it seems to work ;-) ```