On Mar 20, 2015 1:07 PM, "Abilio Marques" <abili...@gmail.com> wrote: > > Yeah, stash is the way I do all the time, but sometimes I want to exclude binaries that are regenerated each time a change and compilation occurs, until I'm ready to the new version to go into trunk. > > Top of my mind, the PDF files that are generated when I use LaTeX. I want to keep the stable version in trunk, yet avoid including binaries that are sometimes hundreds of Kbytes each commit to my "this is just a test" branch, or "this is a modification in progress" branch. I would have to stash the PDFs before each commit (and they are not useful anyway) or type down the entire list of files that I want to include on each commit, which are different each time. > > But by doung fossil ci --ignore file1.pdf file2.pdf -m "here is an example", I can reuse that command 15 times without using the brain harder than a normal "complete" commit will ask me for, until I'm ready to go to the trunk.
Just throwing out an idea: I can see the utility in ignoring certain files on the command line. An ignore switch fits with other commands which take an ignore glob on the command line (I think). The extended thought that came to mind was a new command like "fossil pause", which would not remove a file from the repo, probably would only apply to the working copy, but would stop committing updates to paused files until unpaused. For those of us that use the interactive commenting feature at commit, it could easily provide a list of not only what files are included in the commit, but what files are updated but paused. Or maybe it is a solution in search of a problem.
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
