git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Shawn Pearce <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: Re: Error writing loose object on Cygwin
Date: Tue, 11 Jul 2006 21:15:38 -0700	[thread overview]
Message-ID: <7vr70r1ms5.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20060712035746.GA7863@spearce.org> (Shawn Pearce's message of "Tue, 11 Jul 2006 23:57:46 -0400")

Shawn Pearce <spearce@spearce.org> writes:

> Has anyone else seen this type of behavior before?  Any suggestions
> on debugging this issue?

I would suggest raising this (politely) to Cygwin people.

  reply	other threads:[~2006-07-12  4:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-12  3:57 Error writing loose object on Cygwin Shawn Pearce
2006-07-12  4:15 ` Junio C Hamano [this message]
2006-07-12  4:36   ` Linus Torvalds
2006-07-12  5:00     ` Shawn Pearce
2006-07-13  4:27       ` Junio C Hamano
2006-07-13  5:51   ` Christopher Faylor
2006-07-14  3:34     ` Shawn Pearce
2006-07-14  5:24       ` Christopher Faylor
2006-07-14  5:26       ` Linus Torvalds

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=7vr70r1ms5.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=git@vger.kernel.org \
    --cc=spearce@spearce.org \
    /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).