From: Sverre Rabbelier <srabbelier@gmail.com>
To: Shaun Cutts <shaun@cuttshome.net>
Cc: Git List <git@vger.kernel.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Daniel Barkalow <barkalow@iabervon.org>
Subject: Re: git index: how does it work?
Date: Wed, 5 Aug 2009 11:21:00 -0700 [thread overview]
Message-ID: <fabb9a1e0908051121m6efafc02gd468a92784a73ecd@mail.gmail.com> (raw)
In-Reply-To: <loom.20090805T160528-69@post.gmane.org>
Heya,
On Wed, Aug 5, 2009 at 09:21, Shaun Cutts<shaun@cuttshome.net> wrote:
> PS I'm considering writing an extension to git where the "diff" understands the
> semantics of certain types of files: hunks wouldn't just be textual blobs but
> would try to represent a minimal change from one version to the next based on an
> edit distance, so that, e.g. changing the location of a function would be
> represented by a "move" edit, rather than two text changes.
This sounds very similar to what Daniel was discussing in "[PATCH 2/3
v3] Use an external program to implement fetching with curl git" [0],
if you're truly interested in doing this, please do keep me posted
(and I suspect Dscho might also be interested in being cc-ed) :).
[0] http://thread.gmane.org/gmane.comp.version-control.git/124503
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2009-08-05 18:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-05 16:21 git index: how does it work? Shaun Cutts
2009-08-05 18:00 ` Junio C Hamano
2009-08-12 11:52 ` Shaun Cutts
2009-08-12 17:47 ` Sverre Rabbelier
2009-08-12 18:45 ` Shaun Cutts
2009-08-12 19:39 ` Björn Steinbrink
2009-08-12 20:31 ` Junio C Hamano
2009-08-05 18:21 ` Sverre Rabbelier [this message]
2009-08-05 19:31 ` Shaun Cutts
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=fabb9a1e0908051121m6efafc02gd468a92784a73ecd@mail.gmail.com \
--to=srabbelier@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=shaun@cuttshome.net \
/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