On Thu, Aug 15, 2013 at 11:24:57AM -0400, Richard Hipp wrote: > On Thu, Aug 15, 2013 at 11:11 AM, John Long <[email protected]> wrote: > > > > > Ok so would you mind explaining how you deal with this issue? Are you > > manually adding stuff, or just adding .c and .h files, or ?? > > > > I add and remove files from configuration management individually and > manually. Adding and removing files does not happen that often. Look back > through the Fossil or SQLite history and see how many times files are > added, removed, or renamed. Short answer: seldom.
Thanks. Ok. I had no idea how you are using fossil. This helps explain it. > I also tend to organize projects so that the build happens separately from > the source tree. That facilitates doing multiple builds, with different > compilers (clang/gcc), different compile-time options or targeting > different platforms, from the same source tree. This also makes grepping > easier if the source directory isn't filled up with build products. So > nothing other than source files ever appear in the source tree and > "addremove" would work fine even if I were to use it frequently. I also use multiple compilers but build in-tree just because what I write for UNIX doesn't involve hundreds of source files. I'm not a UNIX guy and I don't know how to do alot of fancy stuff. I'm sure most of the things I do could be done better. That is one of the reasons I asked about this. > I'm curious as to what kind of workflow you are using that requires you to > "addremove" with such frequency that doing so is a burden. When I use fossil for a new project it's easier to add things I want tracked as I go. But sometimes on a productive day I'll add a bunch of doc and a few new programs and a bunch of programs to test those programs and it seems easier to just do an addr and then I usually regret it and have to rm several pieces I didn't want in the project. I also put some (very) old projects with a couple hundred files under fossil to help me understand how fossil works and then I don't have the advantage of knowing everything I want tracked and I find I often miss something or add files I didn't want added. When fossil picks up all the binary stuff it's painful. I do often get a question on commit about binary globs but I haven't looked into exactly when it happens or how commit knows but there isn't a convenient way to ignore all binary files. /jl _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
