code movements in diffs, was Re: [PATCH 2/2] Allow fetch-pack to decide keeping the fetched pack without exploding
From: Johannes Schindelin <hidden>
Date: 2016-06-15 22:42:50
Hi, On Tue, 23 Jan 2007, Jakub Narebski wrote:
quoted hunk ↗ jump to hunk
Johannes Schindelin wrote:quoted
P.S.: These patches make me dream of yet another diff format enhancement: code moves! Of course, for this to be really usable, you'd also have to automatically determine indent changes... You may say I'm a dreamer. But I'm not the only one...I wonder if it could be done with e.g.--- a/fromfile +++ b/somefile<code movement or copying>--- a/somefile +++ b/somefile<other changes> The problem is that context differs usually for code movement.
There is a more fundamental problem here: both "diff" and "patch" walk the file pair in a direction. The whole "code movement" stuff would break this paradigm. What you found is just _one_ consequence. But as I said: a man can still dream, can't he? Ciao, Dscho