code movements in diffs, was Re: [PATCH 2/2] Allow fetch-pack to decide keeping the fetched pack without exploding

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On Tue, 23 Jan 2007, Jakub Narebski wrote:

> Johannes Schindelin wrote:
> 
> > 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

-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]