On 30 July 2015 at 00:07, Joe Mistachkin <[email protected]> wrote: > > Michai Ramakers wrote: >> >> I was unclear; this is the corresponding timeline: >> >> === 2015-07-29 === >> 19:58:39 [70b61c707b] *CURRENT* x (user: michai tags: trunk) >> DELETED d/dd/f >> DELETED d/f >> ADDED e/dd/f >> ADDED e/f >> 19:57:26 [998d26af68] a (user: michai tags: trunk) >> ADDED d/dd/f >> ADDED d/f >> 19:56:53 [07d0f795af] initial empty check-in (user: michai tags: trunk) >> > > Yeah, I've seen that happen to; however, in this case I believe it's a > red herring. The --hard option makes no different in how the timeline > is presented. > > I'm not saying there isn't an issue with the timeline; I'm saying it's > unrelated to the --hard option.
alright; I'll test this more in the afternoon. But looking at it now: what is the net difference (then) between... 1) mv dir1 dir2 2) fossil addremove 3) fossil checkin ...and... 1) fossil mv --hard dir1 dir2 2) fossil addremove 3) fossil checkin ..? (The history of files within the new 'dir2' is broken in either case, I think.) Michai _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
