On Wed, Mar 12, 2014 at 1:13 PM, JR <jr...@saintlyreverend.com> wrote:
> I host my fossil repository on a private server. As a little background, > I do mostly scripting work and keep all my "projects" in separate branches. > This has worked great for me and I will continue to use this method. > However, I am almost finished with a project I would like to host on > chiselapp so the greater Internet can reach it. > .... > I have run <fossil export>, but the resulting file for my repository is > too large for me to realistically manually edit down to just the branch I > want. If anybody has some scripting-fu for that, that would be awesome. > In theory, a script could use SQL to identify the artifacts for a specified branch. then create a shun list of the artifacts for the other branches. Alternately, SQL could be used to load those artifacts in a new repository. Another possible option would be to use "fossil deconstruct" to extracts the artifacts into files, then copy the desired artifacts to another directory and use "fossil reconstruct". I suspect there are some other artifacts that will also need to be copied in order to create a valid repository. Caveat: For all of these options, each repository created this way will have the same repository ID as the original, so it would be possible to accidentally push undesired content in to any of them.
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
