Re: [fossil-users] copying a branch and history into a new repository
On Wed, Mar 12, 2014 at 6: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. My Google-fu seems ... Otherwise, does anybody have any other ideas? Thanks. AFAIK there is no reasonable way to accomplish what you're trying, but one of the feature's i'd like to eventually add to libfossil is somewhat close: the ability to export a repository from it's starting point up to a specific point in time. i.e. export until version ABCD. It's not possible to cut out prior history (that would break hashing), but it should be fairly safe/straightforward to export up to a given cutoff point. Also, Stephan Beal, I cannot wait until libfossil can be used natively on Windows (without Cygwin). I have some ideas for using it in my workflow... Jan recently got it compiling warning-free on Cygwin, but AFAIK nobody has yet tried it on Windows (and i don't have/use Windows). In theory the current code will build on Windows (if you create your own build files - we currently only have GNU-make Makefiles). Any reports of success (or contributions of build files) would be greatly appreciated :). -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do. -- Bigby Wolf ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] copying a branch and history into a new repository
2014-03-13 10:32 GMT+01:00 Stephan Beal sgb...@googlemail.com: Jan recently got it compiling warning-free on Cygwin, but AFAIK nobody has yet tried it on Windows (and i don't have/use Windows). In theory the current code will build on Windows (if you create your own build files - we currently only have GNU-make Makefiles). Any reports of success (or contributions of build files) would be greatly appreciated :). I will see what I can do. Usually before trying it on win32, I try it on Cygwin first, but since that's done nothing (except available time) stops me from going on. A MinGW build can re-use the GNU buildfiles. Regards, Jan Nijtmans ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] copying a branch and history into a new repository
@JR: Jan just took us one step closer: http://fossil.wanderinghorse.net/repos/libfossil/cgidemo/index.cgi/manifest/f994fec9c568dbbb -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do. -- Bigby Wolf ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] copying a branch and history into a new repository
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
Re: [fossil-users] copying a branch and history into a new repository
My SQL is not so great, but I could work with this and de/reconstruct. Thanks for the ideas. I have needed an excuse to dig deeper into the capabilities of Fossil since I joined the list and see people talking about custom SQL statements, the construct commands, and other advanced uses. Looks like I have a mini-project (yet another one!) for the next few weeks. JR On Thu, Mar 13, 2014 at 12:08 PM, Ron Wilson ronw.m...@gmail.com wrote: 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 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] copying a branch and history into a new repository
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. My Google-fu seems to have failed me and this was the best search I could come up, fossil branch history new repository. I only found one try that did not talk about just branching an existing repository and this mailing list entry from January 2012http://www.mail-archive.com/fossil-users%40lists.fossil-scm.org/msg07227.htmldoes not have any responses to 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. I am on Windows, but any language will work; I can port the functionality to a Windows scripting language for my purposes (and would happily share that back with the list). Otherwise, does anybody have any other ideas? Thanks. Also, Stephan Beal, I cannot wait until libfossil can be used natively on Windows (without Cygwin). I have some ideas for using it in my workflow... JR ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
