threads / discuss / 13822
Subject: git-clone still broken wrt. unpacking working tree with http transport
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 <http://moonbase.rydia.net/software/optimized-locking/optimized-locking.git/ >.
-Kevin Ballard
-- Kevin Ballard kevin@rapleaf.com
Jeff KingRe: git-clone still broken wrt. unpacking working tree with http transport
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
Re: git-clone still broken wrt. unpacking working tree with http transport
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 HamanoRe: git-clone still broken wrt. unpacking working tree with http transport
Kevin Ballard <kevin@rapleaf.com> 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 ;-)