git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Pavel Roskin <proski@gnu.org>
Cc: git@vger.kernel.org
Subject: Re: git 1.5.1-rc1 doesn't like empty files
Date: Mon, 19 Mar 2007 21:54:01 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0703192148430.6730@woody.linux-foundation.org> (raw)
In-Reply-To: <1174361424.3143.42.camel@dv>



On Mon, 19 Mar 2007, Pavel Roskin wrote:
> 
> I don't know where this problem appeared, but it present in the current
> git (1.5.1-rc1).  Empty files become invalid objects in the repository:

Hmm.. Not for me. Can you bisect when it started happening?

> This is Linux, Fedora Development, i386.

FC6, tested both i386 and x86-64.

I wonder if this is a zlib issue. Although I seem to have libz-1.2.3 on 
both machines, and that should be the most recent version. I don't see 
Fedora development having anything else..

		Linus

  parent reply	other threads:[~2007-03-20  4:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-20  3:30 git 1.5.1-rc1 doesn't like empty files Pavel Roskin
2007-03-20  4:24 ` Nicolas Vilz
2007-03-20  4:54 ` Linus Torvalds [this message]
2007-03-20  5:08   ` Pavel Roskin
2007-03-20  5:41     ` Linus Torvalds
2007-03-20  5:50       ` Pavel Roskin
2007-03-20  5:56       ` Shawn O. Pearce
2007-03-20  7:04       ` Alexander Litvinov
2007-03-20  8:43       ` Andy Parkins
2007-03-20  8:49         ` Junio C Hamano
2007-03-20  9:26           ` Andy Parkins
2007-03-20 15:45             ` Linus Torvalds
2007-03-20  5:29 ` Junio C Hamano
2007-03-20  5:47   ` Pavel Roskin
2007-03-20  5:49   ` Linus Torvalds
2007-03-20  6:00     ` Junio C Hamano
2007-03-20  6:05       ` Junio C Hamano
2007-03-20 15:46         ` 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=Pine.LNX.4.64.0703192148430.6730@woody.linux-foundation.org \
    --to=torvalds@linux-foundation.org \
    --cc=git@vger.kernel.org \
    --cc=proski@gnu.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).