Thus said Harry Putnam on Mon, 09 Feb 2015 20:03:28 -0500: > I'm not so concerned about losing my experimental repo recoreds of its > files. I was trying to ask if I could acquire a much larger set of > files by moving my current repo db file and then go to the highest > level of this specific hierarchy and just say `add .' to greatly > expand that repo. The `add' would also includ the existing repo > files but the repo would then include a much larger selection of > nowversioned files.
It sounds like you have something like: x/y/z Where you have added the files from z into the root of a repository and now you want to add x/y. So, why not just copy x/y (without z), add/commit them, and then use fossil rename and move z back to the x/y in the repository? You can do this all in a test clone of your repository to see if you like how it works out. > I understand that the history of changes for the files already > versioned would be lost. Subsumed by the bigger repo. Unless you use fossil rename. If this is not correct, please provide more details. Andy -- TAI64 timestamp: 4000000054d95d96 _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
