Yann Dirson <ydirson@xxxxxxxxxx> writes:
> I hope I just miss your point. Letting unaware tools handle such a
> patch "the right way" would imply just adding the information "dir foo
> moved to bar", and not removing the individual file moves, which goes
> in the way of the exact reason why I have started to work on this.
If your change is to move a/{1,2,3} to b/{1,2,3} and without content
change to a/{1,2} to b/{1,2}, then do you want to say "a/ moved to b/
and by the way here is the content change from a/3 to b/3" without saying
anything about a/{1,2} and b/{1,2}?
Two points.
* I do not think it is a good idea to begin with. If you are to apply
such a patch (with git-apply that is updated with your patch to
understand that notation) to the exact tree that has only {1,2,3} under
a/, you would get an expected result. But if the recipient of your
patch has a/4 (or lacks a/2), there is no cue in the patch that
automatically moving a/4 to b/4 may or may not be what is sane (or the
patch is unapplicable in general).
* If you give at least the names of paths that were moved without any
content changes as I suggested, at least the recipient of your patch
can catch the case where his tree is structurally different from what
you used to prepare the patch for by noticing the a/2 in the patch that
he does not have.
In addition, if you keep the movements for the paths whose contents did
not change, existing tools are perfectly capable of applying (or showing)
the output. I seriously doubt that keeping 4 lines per perfectly moved
paths is too much a price to pay to keep backward compatibility.
> Compare this to the addition of the "file rename" feature (correct me
> if I'm wrong): it was added without bothering whether plain old
> "patch" can deal with it,...
Sorry, but that's an old history whie git-diff output format was rapidly
being developed, when we did not have that many users, and when we did not
have an old version of git-apply that did not understand the new feature
in majority of user's hands.
We do not have that kind of luxury anymore. git is much more widespread
now and the majority of people use pre-1.6.1 git now (including me ;-)).
--
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
