On 2/12/2016 8:45 AM, Warren Young wrote:
While doing the tests detailed in my other thread (delta.c assertion
failure on Linux) I came across two other oddities that seem like
unrelated issues, so I’m starting a new thread for them.
I think Ross Berteig ran into some of this, so please forgive any
redundancy. I didn’t want these separate issues to get lost in the
other thread.
Redundancy is probably good ;-)
While cd’d into a fossil-scm.org repo checkout, run these commands:
....
I added this to the (growing) test/stash.test, working in a newly
created repository. I create two files: f1 and f2, add them, and commit.
Then I f mv --hard f2 f2n and stash.
Notice two odd behaviors:
1. Apparently every file in the repository has an empty diff saved
with it. (Confirmed by the “stash show” command.)
And by the output of stash save, which said:
REVERT f1
REVERT f2
DELETE f2n
Stash show also mentions f1 with no changes. Oddly, it mentions f2n as
having no changes and is silent about its name changing from f2. Now I'm
curious what fossil revert and fossil diff say when the only changes
were renames. I'll go poke at that "soon".
> 2. The file rename is not rescheduled. It says:
MISSING zip.c
Reproduced in the test case. Which I will commit any minute now.
While comparing to a similar sequence with an added f3 instead of a
rename, I noticed another anomaly which I will try to paint into a
corner next.
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineering Corp. http://www.CheshireEng.com/
+1 626 303 1602
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
