On Mon, 18 Nov 2013 15:18:37 +0100, Richard Hipp <[email protected]> wrote:
On Mon, Nov 18, 2013 at 8:21 AM, j. van den hoff
<[email protected]>wrote:
it seems that after `fossil mv name.old name.new' (plus `mv name.old
name.new') and further `fossil ci name.new' actions.
fossil correctly states in the `file history' of `name.old' and
`name.new'
that a rename has occurred but it
seemingly cannot neither show a fused `file history' nor a diff across
the
rename.
simple question: is that just the state of affairs or are there ways to
access the full history of the renamed file (notably for diffs)?
I thought that diffs across renames was working. I'll have to look into
it.
hope I don't make a stupid error...
to be specific, the rename was of the sort:
fossil mv oldname newdir/newname
so the file now resides in a different (newly created) subdir of the
checkout, too, if this makes a difference.
what I observe is the following: say, I have created a checkin [1234]
after the rename (or this is the "renaming" checkin) and [abcd] is a
revision prior to the rename. then
1.
fossil diff -r abcd newdir/newname
fossil diff -r abcd --to 1234 newdir/newname
yield
file newdir/newname does not exist in checkin: abcd...
2.
fossil diff -r abcd --to 1234 oldname
yields
file oldname does not exist in checkin: 1234
3.
fossil diff -r abcd oldname
lists as changes that all lines from `oldname' have been removed, i.e. it
diffs
--- oldname
+++ /dev/null
all of which of course are correct if the rename is not recognized but not
otherwise AFAICS. if I'm not making a stupid error ...
j.
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
