From: Nicolas Pitre <nico@cam.org>
To: Alex Riesen <raa.lkml@gmail.com>
Cc: git@vger.kernel.org,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Junio C Hamano <junkio@cox.net>
Subject: Re: [PATCH] Fix git-fast-export for zero-sized blobs
Date: Tue, 11 Dec 2007 17:20:38 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.0.99999.0712111719380.555@xanadu.home> (raw)
In-Reply-To: <20071211220128.GA19857@steel.home>
On Tue, 11 Dec 2007, Alex Riesen wrote:
> Signed-off-by: Alex Riesen <raa.lkml@gmail.com>
> ---
> builtin-fast-export.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> Nicolas Pitre, Tue, Dec 11, 2007 21:27:33 +0100:
> > Simply doing something like:
> >
> > $ git fast-export --all > /dev/null
> >
> > results in:
> >
> > fatal: Could not write blob e69de29bb2d1d6434b8b29ae775ad8c2e48c5391
> >
>
> I get this for my git repo:
>
> $ git fast-export --all >/dev/null
> fatal: Could not write blob e69de29bb2d1d6434b8b29ae775ad8c2e48c5391
> $ git cat-file blob e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 |wc -c
> 0
>
> Writing a zero-size blob will surely returns 0.
Indeed.
/me looking at too many piece of code at the same time
Nicolas
next prev parent reply other threads:[~2007-12-11 22:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-11 20:27 'git fast-export' is crashing on the gcc repo Nicolas Pitre
2007-12-11 20:35 ` Marco Costalba
2007-12-11 22:01 ` [PATCH] Fix git-fast-export for zero-sized blobs Alex Riesen
2007-12-11 22:20 ` Nicolas Pitre [this message]
2007-12-11 22:06 ` 'git fast-export' is crashing on the gcc repo Nicolas Pitre
2007-12-12 1:38 ` Alex Riesen
2007-12-12 1:45 ` Nicolas Pitre
2007-12-12 8:32 ` Junio C Hamano
2007-12-12 8:46 ` David Kastrup
2007-12-12 8:56 ` Junio C Hamano
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=alpine.LFD.0.99999.0712111719380.555@xanadu.home \
--to=nico@cam.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=raa.lkml@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).