* git-clone still broken wrt. unpacking working tree with http transport
@ 2008-06-05 23:48 Kevin Ballard
2008-06-06 6:14 ` Jeff King
0 siblings, 1 reply; 4+ messages in thread
From: Kevin Ballard @ 2008-06-05 23:48 UTC (permalink / raw)
To: Git Mailing List
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: git-clone still broken wrt. unpacking working tree with http transport
2008-06-05 23:48 git-clone still broken wrt. unpacking working tree with http transport Kevin Ballard
@ 2008-06-06 6:14 ` Jeff King
2008-06-06 23:28 ` Kevin Ballard
0 siblings, 1 reply; 4+ messages in thread
From: Jeff King @ 2008-06-06 6:14 UTC (permalink / raw)
To: Kevin Ballard; +Cc: Git Mailing List
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: git-clone still broken wrt. unpacking working tree with http transport
2008-06-06 6:14 ` Jeff King
@ 2008-06-06 23:28 ` Kevin Ballard
2008-06-06 23:30 ` Junio C Hamano
0 siblings, 1 reply; 4+ messages in thread
From: Kevin Ballard @ 2008-06-06 23:28 UTC (permalink / raw)
To: Jeff King; +Cc: Git Mailing List
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: git-clone still broken wrt. unpacking working tree with http transport
2008-06-06 23:28 ` Kevin Ballard
@ 2008-06-06 23:30 ` Junio C Hamano
0 siblings, 0 replies; 4+ messages in thread
From: Junio C Hamano @ 2008-06-06 23:30 UTC (permalink / raw)
To: Kevin Ballard; +Cc: Jeff King, Git Mailing List
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 ;-)
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2008-06-06 23:31 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-06-05 23:48 git-clone still broken wrt. unpacking working tree with http transport Kevin Ballard
2008-06-06 6:14 ` Jeff King
2008-06-06 23:28 ` Kevin Ballard
2008-06-06 23:30 ` Junio C Hamano
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).