-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Cool, thanks for the note about rebuild. I had already run that a few times after shunning and it worked fine, so I'm glad to know that this is a reliable indicator that integrity is OK.
Any thoughts on why I can't check out the first, empty commit? I just tried on another test repository and it works fine, but in http://dev.thewordnerd.info/hermes I'm told that it isn't a commit. Thanks for the quick response. On 09/09/2010 06:42 AM, Richard Hipp wrote: > On Thu, Sep 9, 2010 at 6:52 AM, Nolan Darilek <[email protected]>wrote: > > Hello. > > Last night I decided to convert one of my larger, unreleased projects to > Fossil, and to try a soft launch to see how I like it. Only, my > conversion process was somewhat convoluted, and I have this fear that > while it looks OK in the web interface and seems to check out fine, that > there's something waiting to bite me. > > >> If "fossil rebuild" works, then you should be OK. > >> Fossil was never really designed to have multiple independent branches. The >> idea is that everything would descend from a single ancestor check-in. The >> "Adam" node, I suppose you could call it. But you seem to have configured >> things to have multiple independent branches in the same tree. It seems to >> work, and I cannot (off the top of my head) think of any reason why it >> shouldn't work. Let us know if you run into any problems.... > > > > I wanted a multi-project setup as I've mentioned here previously, and > had a pile of 3 Git repositories. To import, I ran the importer posted > here a while back, editing the script and replacing instances of "trunk" > with the desired tag for each project. I then created an entirely new > fossil, dumped its config table to SQL, then replaced the config tables > in each of the newly-created repositories in order to quickly give them > the same IDs. I then launched each project via the web interface, synced > them with the newly-created fossil, and after about an hour or so in the > web interface deleting unwanted tags and fixing continuity breaks, I > have what appears to be a multi-project setup here: > > http://dev.thewordnerd.info/hermes > > Two quick things. > > 1. Does anything seem immediately and obviously wrong with my > conversion? I did a bit of shunning of control artifacts (I didn't want > "master" or "trunk" tags on many of my commits) and there are spots > where branch continuity broke because the importer generated a rogue > leaf at a Git merge. As a result, I had to close a leaf created in > February, then retag commits after that with the same branch name. This > seems like it should be fine, and appears so in the timeline, but I > still feel a bit out of my league with this problem. :) > > 2. I want to use embedded documentation for the website, but I'm not > sure how to get started. What I mean is that I want to start with an > empty commit populated with .wiki files to create a hierarchy, but when > I try opening ceab (which I've also tagged "empty") I'm told that it > isn't a commit. This is why I'm wondering if perhaps I broke something > in my import process, or maybe there's some other way to get an empty > commit for an entirely new branch? > > Thanks for reading, and for answering my various questions over the past > week. :) >> _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users >> > _______________________________________________ > fossil-users mailing list > [email protected] > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkyI1CMACgkQIaMjFWMehWIBnQCfVCVbrfpFEF/ggL/7W5gbBpsK RRoAniLsB4VFLDNfbf+mPKCvMRV2SfOZ =iSNN -----END PGP SIGNATURE----- _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
