[Default] On Fri, 20 Mar 2015 14:36:51 -0430, Abilio Marques
<[email protected]> 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.
Will something like
fossil ci -m "example" $(fossil changes|grep -v .pdf|awk '{print $2}')
do what you intend?
It is repeated as easily as the --ignore solution.
--
Regards, Cordialement, Groet,
Kees Nuyt
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
