git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Erik Faye-Lund <kusmabite@gmail.com>
To: ZoltánFüzesi <zfuzesi@eaglet.hu>
Cc: git@vger.kernel.org
Subject: Re: msysgit clone/pull/fetch broken
Date: Thu, 2 Dec 2010 13:43:50 +0100	[thread overview]
Message-ID: <AANLkTi=cPj2poOpZa3M-UVjQmjQ3BKj3FBJHQc_+Z6Vb@mail.gmail.com> (raw)
In-Reply-To: <loom.20101202T081807-557@post.gmane.org>

On Thu, Dec 2, 2010 at 8:28 AM, ZoltánFüzesi <zfuzesi@eaglet.hu> wrote:
> Erik Faye-Lund <kusmabite <at> gmail.com> writes:
>
>>
>> On Wed, Dec 1, 2010 at 2:31 PM, ZoltánFüzesi <zfuzesi <at> eaglet.hu> wrote:
>> > Hi, I can't clone/pull/fetch from any of my repositories with the latest
> stable
>> > version (1.7.3.2.430.g208247) on Windows.
>> >
>> > $ git clone --recursive git://server/user/project.git
>> > Cloning into project...
>> > fatal: failed to read object <sha1>: No error
>> >
>> > After reverting commit 3ba7a065527a27f45659398e882feaa1165cbb4c ("A loose
> object
>> > is not corrupt if it cannot be read due to EMFILE") it works.
>> >
>> > On Linux everything is fine.
>>
>> I've already submitted a patch-series that address this issue:
>> <1290533444-3404-1-git-send-email-kusmabite <at> gmail.com>
>>
>
> Thanks! Could you give me the sha1(s) of those patches? I've found some of your
> recent patches, but they have already been merged into master.
>

I don't think the patches has been merged yet, so I don't really have
a SHA-1 for the series. But you could pull the topic from
git://repo.or.cz/git/kusma.git work/win32-dirent

  reply	other threads:[~2010-12-02 12:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-01 13:31 msysgit clone/pull/fetch broken ZoltánFüzesi
2010-12-01 13:37 ` Erik Faye-Lund
2010-12-02  7:28   ` ZoltánFüzesi
2010-12-02 12:43     ` Erik Faye-Lund [this message]
2010-12-02 17:48       ` ZoltánFüzesi

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='AANLkTi=cPj2poOpZa3M-UVjQmjQ3BKj3FBJHQc_+Z6Vb@mail.gmail.com' \
    --to=kusmabite@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=zfuzesi@eaglet.hu \
    /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).