As I said, I did not DELETE any files, but rather moved them. fossil changes reported them as RENAMED. And in the check in, they are being reported as DELETED.
I'm just asking how in the design of Fossil you justified this decision. Please directly address this vs skirting it. ^K on Dec 17, 2012, Richard Hipp <d...@sqlite.org> wrote: > > > >On Mon, Dec 17, 2012 at 2:55 PM, K <k...@lightpowered.org> wrote: > > > > > >I'm looking at the page for my file and its history ends as deleted when I did >not >delete it. I moved it, which fossil changes reported as a RENAMED. I commited >and >now have the surprise dumped on me that my file was deleted and whatever else, >when >it was not. This is not acceptable to lose the history of a file just because >I MOVE >it. I cannot believe this is how Fossil is operating and apparently is >expected to >operate. PLEASE JUSTIFY THIS. > > > > > >I've very sorry that the file history report does not structure the >information as >you would prefer. > >All of the information needed to track file changes across renames is >contained in >the repository. And, in fact, the "annotate" screens do trace changes across >renames. >But nobody has yet taken the time to write a report screen that displays a >file history >graph across renames. Perhaps because nobody cares as passionately about this >as >you seem to. The Fossil source code is open-source; you could contribute a >solution >if you wanted to. > > > >-- >D. Richard Hipp >d...@sqlite.org > > > >_______________________________________________ >fossil-users mailing list >fossil-users@lists.fossil-scm.org >http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
