I forgot to do something about the `to standard output` bit. We could leave it like that, but if the user forgets to redirect, he'll get a messy terminal. Perhaps we could add a final argument: FILE, so we'd have:
Usage: fossil export FORMAT ?OPTIONS? ?REPOSITORY? ?FILE? Write an export of all check-ins to FILE in one of the following repository FORMATs: --fossil the fossil format --git the git-fast-export format If FILE is not specified or is "-", write export check-ins to standard output. On 27 July 2016 at 06:04, Barry Arthur <barry.art...@gmail.com> wrote: > I like the `export` idea. It solves the `trash-can` problem and it's a > feature that has been (directly or indirectly) requested a few times over > the years. That covers (a) and (c), only leaving: > > (B) Define the syntax of ARGS. > > > Let me begin that bikeshed with: > > Existing tools: > > find . -type f -name "*.txt" ! -path "./Movies/*" ! -path "./Downloads/*" > ! -path "./Music/*" > rsync -avz --exclude 'dir1' --exclude file1.txt --exclude dir3/*.txt > source/ destination/ > rsync -avz --exclude-from 'exclude-list.txt' source/ destination/ > > Fossil proposal: > > Usage: fossil export FORMAT ?OPTIONS? ?REPOSITORY? > > Write an export of all check-ins to standard output in one of the following > repository formats: > --fossil the fossil format > --git the git-fast-export format > > Run this command within a checkout. Or use the -R or --repository > option to specify a Fossil repository to be exported. > > Only check-ins are exported using --git. Git does not support tickets > or wiki or events or attachments, so none of those are exported. > > If the "--import-marks FILE" option is used, it contains a list of > rids to skip. > > If the "--export-marks FILE" option is used, the rid of all commits and > blobs written on exit for use with "--import-marks" on the next run. > > Use the "--exclude GLOB" option to prevent matching files and/or > directories > from being exported. It can be used as many times as you like to build up > the list of files to exclude. > > Use the "--exclude-from FILE" option to exclude a large number of GLOB > patterns conveniently. > > Options: > --exclude GLOB don't export GLOB > --exclude-from FILE don't export GLOBS within FILE > --export-marks FILE export rids of exported data to FILE > --import-marks FILE read rids of data to ignore from FILE > --repository|-R REPOSITORY export the given REPOSITORY > > Have at it! > > On 27 July 2016 at 05:13, Richard Hipp <d...@sqlite.org> wrote: > >> On 7/26/16, David Mason <dma...@ryerson.ca> wrote: >> > Is there any way to find all the artifacts that correspond to a given >> > pathname? Then I could shun those. >> >> SELECT DISTINCT uuid >> FROM blob, mlink, filename >> WHERE blob.rid=mlink.fid >> AND mlink.fnid=filename.fnid >> AND filename.name=$NAME; >> >> Fill in $NAME appropriately, of course. >> >> -- >> D. Richard Hipp >> d...@sqlite.org >> _______________________________________________ >> fossil-users mailing list >> fossil-users@lists.fossil-scm.org >> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users >> > >
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
