On Tue, Feb 10, 2015 at 4:06 AM, Harry Putnam <rea...@newsguy.com> wrote:
> The directory hierarchy I'm working in is was to be the /projects > directories and files from several divergent hosts that have been > rsync'ed onto a solaris host, > > Each host to have its own hierarchy, so there would be a lot of > duplicaiton and near duplication that I'd like to clean up much as I > can. The near dups will need to be merged some way. I'm still > pondering that but the whole thing could still be in one fossil repo > If it is only a matter of hierarchical directory structure then it should be simple, but let's see what you've got... > If I expand the repo like I've posted about it would grow a good bit > but still probably fall into the tiny catetogry by many of the posters > here standards. > > Expanded it would be > 18,022 files in: > 1,311 directories > FWIW, i'd call that mid-sized. In my experience most fossil repos are well under 2k files and a few dozen directories. The canonical fossil repo (mine is a bit out of date, but not too much): [stephan@host:~/cvs/fossil/fossil]$ find . -type f | wc -l 1476 [stephan@host:~/cvs/fossil/fossil]$ find . -type d | wc -l 179 And the sqlite3 repo is smaller. See them at (two files): > > http://zeus.jtan.com/~reader/vu1/disp.cgi So your goal is to basically "overlay" the 2x and dv projects into one tree, such that the 2x/perl dir is at the same level as the dv/awk dir, right? If that is correct, then i would proceed as follows (or this is what i would try first)... - Create a new project dir (or use one of the projects as the new home for all others) - rsync (or cp -r) all projects into that new top dir. - fossil add . - use (fossil status) to make sure no useless stuff got imported (e.g. temp files and such), and use fossil rm to remove (before committing!) any such files. If there are duplicate files, e.g. xyz/abc and zyx/def, fossil will treat them as two logical files but (because they have the same hash) only stores them once (so they effectively become "copy on write" if one is changed and the other is not). Fossil support symlinks, which you could use to eliminate dupes, but i've always avoided symlinks in source control because they are inherently platform-specific. Does that answer your question? -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
