From: Johannes Sixt <j.sixt@viscovery.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Nick Edelen <sirnot@gmail.com>
Subject: Re: What's cooking in git.git (Jul 2009, #01; Mon, 06)
Date: Tue, 07 Jul 2009 08:30:39 +0200 [thread overview]
Message-ID: <4A52EB8F.1010806@viscovery.net> (raw)
In-Reply-To: <7vk52l4q7k.fsf@alter.siamese.dyndns.org>
Junio C Hamano schrieb:
> * ne/futz-upload-pack (Wed Jun 10 01:50:18 2009 +0200) 1 commit
> - Shift object enumeration out of upload-pack
I'm interested in this one because it is a step towards improved behavior
of upload-pack on Windows if the repository is corrupted[*]. This patch
covers the common case where shallow clones are out of the game, but it is
not ready for prime time until its implementation is complete. IIUC, this
should be a fall-out of a GSoC project. Until then I include it in my git.
[*] One test case in t5530 still fails on Windows, because for some reason
errors are not reported correctly. It has to do with the rev-list being
run in a thread and that thread die()s.
-- Hannes
next prev parent reply other threads:[~2009-07-07 6:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-06 18:32 What's cooking in git.git (Jul 2009, #01; Mon, 06) Junio C Hamano
2009-07-06 20:29 ` Marcus Camen
2009-07-06 21:38 ` Junio C Hamano
2009-07-06 22:03 ` Marcus Camen
2009-07-06 22:34 ` Junio C Hamano
2009-07-06 23:42 ` Jakub Narebski
2009-07-07 2:18 ` Mark Lodato
2009-07-07 21:11 ` Jeff King
2009-07-07 6:30 ` Johannes Sixt [this message]
2009-07-07 19:17 ` Linus Torvalds
2009-07-07 19:57 ` Alex Riesen
2009-07-07 22:13 ` Linus Torvalds
2009-07-07 20:08 ` Johannes Schindelin
2009-07-07 20:13 ` Shawn O. Pearce
2009-07-07 22:19 ` Junio C Hamano
2009-07-07 22:28 ` Shawn O. Pearce
2009-07-08 13:42 ` notes, was " Johannes Schindelin
2009-07-08 5:39 ` Stephen Boyd
2009-07-08 6:38 ` Johannes Sixt
2009-07-10 5:05 ` Christian Couder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A52EB8F.1010806@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sirnot@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).