From: Nicolas Pitre <nico@cam.org>
To: Peter Eriksen <s022018@student.dtu.dk>
Cc: git@vger.kernel.org
Subject: Re: [RFH] Exploration of an alternative diff_delta() algorithm
Date: Sun, 09 Apr 2006 13:45:00 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0604091340540.2215@localhost.localdomain> (raw)
In-Reply-To: <20060409173409.GB23908@erlang.gbar.dtu.dk>
On Sun, 9 Apr 2006, Peter Eriksen wrote:
> On Sun, Apr 09, 2006 at 01:14:31PM -0400, Nicolas Pitre wrote:
> ...
> > Nothing outside diff-delta.c and patch-delta.c is aware of the delta
> > data format. So if your version is meant to be a transparent
> > replacement then it should pass all tests. If it doesn't then it is
> > broken.
> >
> > To help you play around you could try the test-delta utility (make
> > test-delta to build it).
> >
> > So:
> >
> > test-delta -d file1 file2 delta_file
> > test-delta -p file1 delta_file file3
> > cmp file2 file3
>
> My tests of these kinds doesn't show any errors.
Try this with the README file from the git source tree:
sed s/git/GIT/g < ./README > /tmp/README.mod
test-delta -d ./README /tmp/README.mod /tmp/README.delta
[BOOM!]
> Though, if file2 is empty, test-delta writes: "file2: Invalid
> argument".
We never delta against or towards empty files.
Nicolas
next prev parent reply other threads:[~2006-04-09 17:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-09 14:31 [RFH] Exploration of an alternative diff_delta() algorithm Peter Eriksen
2006-04-09 17:14 ` Nicolas Pitre
2006-04-09 17:34 ` Peter Eriksen
2006-04-09 17:45 ` Nicolas Pitre [this message]
2006-04-09 22:45 ` Peter Eriksen
2006-04-10 3:29 ` Nicolas Pitre
2006-04-09 17:40 ` Nicolas Pitre
2006-04-09 17:53 ` Peter Eriksen
2006-04-09 18:08 ` Nicolas Pitre
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.0604091340540.2215@localhost.localdomain \
--to=nico@cam.org \
--cc=git@vger.kernel.org \
--cc=s022018@student.dtu.dk \
/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