I don't need to make assumptions, and therefore am not. I'm going off of the facts, which I can observe, and which I can present to others.
The file was not deleted. It was moved using Fossil's own "fossil mv" command. It's irrational to treat this as a deletion. If you cannot provide justification for this behavior, we should move to discussing the behavior Fossil should exhibit. ^K on Dec 17, 2012, Richard Hipp <[email protected]> wrote: > > > >On Mon, Dec 17, 2012 at 3:49 PM, K <[email protected]> wrote: > > > >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. > >I would guess that when generating the "DELETED" text the code merely notes >that a >file with that name is no longer part of the check-in and that the code does >not >go to the extra trouble to figure out if the filename changed. > > > >You seem to be making the assumption that whoever wrote that bit of code made >a deliberate >decision to obscure the fact that the filename changed. Why would you assume >that? > > > > > > >^K > > > > > >on Dec 17, 2012, Richard Hipp <[email protected]> wrote: > >> > >> > >> > >>On Mon, Dec 17, 2012 at 2:55 PM, K <[email protected]> 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 > >>[email protected] > >> > >> > >> > >>_______________________________________________ > >>fossil-users mailing list > >>[email protected] > >>http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > >> > >_______________________________________________ > >fossil-users mailing list > >[email protected] > >http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > > > > >-- >D. Richard Hipp >[email protected] > > > >_______________________________________________ >fossil-users mailing list >[email protected] >http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
