On Fri, Aug 9, 2013 at 12:28 PM, j. van den hoff
<[email protected]>wrote:
> so fossil only logs the rename as DELETED plus
> and ADDED action w/o keeping track of the rename any more so a diff can
> only be done manually by extracting both revisions (pre/post rename) from
> the repo?
>
Fossil does keeps track of renames. But the current diff logic does not
make use of that information.
Part of the problem arises from syntax. If you type:
fossil diff --from abc --to cde xyz.txt
Are you meaning the diff the file xyz.txt in version abc against whatever
that file is called in version cde. Or do you mean to diff the xyz.txt in
cde against the equivalent file in abc?
As I sit here and ponder the problem, I think I prefer the current behavior
anyhow. I think the command above should mean to compute the diff between
file called xyz.txt in the two specified versions, regardless of their
relative ancestry. If you want to diff file xyz.txt in one version against
file pqr.txt in another version, you should say so. (That is not something
that the diff command currently supports directly, but it could be added, I
suppose, and I'd be more inclined to add that than to make the diff command
magically track file renames through time.)
The other part of the problem is that I do most of the implementation for
things like this and I rarely ever rename files in a project, so diffing
between two versions of a file whose name has changed is not something that
comes up for me very often, and hence is not a priority. You are more than
welcomed to submit patches if it is a priority for you, though.
--
D. Richard Hipp
[email protected]
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
