On Apr 17, 2009, at 1:21 PM, Erik Lechak wrote: > Hello > > I recently switched a project from mercurial to fossil, and I'm having > some transition pains. I'm sure most of my difficulties stem from the > fact that I just started using fossil and am used to doing things in > other scm-centric ways. > > Hosting a Repository > -------------------- > My web hosting provider does not allow CGI, and I can't run "fossil > serv" on their server. Are there any free fossil-scm hosts out there > for an open source project?
Email me a copy of your repository and I will host it at http://www.fossil-scm.org/YOUR-PROJECT-NAME . Be sure to set your user-id and password first so that you will be able to log in after I move the repository to the server! This same offer stand for anybody else who would like a place to host an open-source project based on fossil. If you have your own project domain name, I'll host your project at http://www.YOUR -PROJECT-DOMAIN/. All of the above goes on the same server as http://www.sqlite.org/ and SQLite will take priority. I'm happy to share the space as long as your bandwidth is reasonable. I find it hard to imagine how a small project could use too much bandwidth so this should not be a concern unless you deliberately try to abuse the server. > > Deleting a Ticket > ----------------- > I added a bug ticket, and I must have clicked the button twice because > it generated two tickets. How do you delete a ticket item? The best thing to do is just close the redundant ticket. Fossil is *designed* to make it hard to delete stuff in order to maintain a detailed audit trail for quality assurance. If you really, really need to delete a ticket you can "Shun" the corresponding artifacts then click the "Rebuild" button on the Shunning page to rebuild the repository without the extra ticket. Shunning is really designed to get rid of inappropriate content (profanity, copyright violations, spam, etc). Shunning is not intended to fix mistakes. So use shunning wisely and sparingly. > > > Copying a Working Directory > --------------------------- > I'm a little confused about what happens when I make a copy of the > directory containing my repository and the source code. They seem to > stay linked somehow. Why is this, how do I stop it from happening, or > is it a feature that I should learn to appreciate? For example: > > I am working on a fossil managed project contained in the XXX > directory. > I want to do something crazy to the code. There's a 95% chance that I > just want to throw all the changes away. So I just make a copy of the > XXX directory. Let's call it YYY. Now, I go into the YYY directory > and > do crazy change 1 then do a "fossil ci". I do crazy change 2 and do a > "fossil ci". If I return to the XXX directory and do a "fossil ti", I > can see the crazy changes I made to YYY. > > In Mercurial the directories are completely compartmentalized. If I > choose to keep the changes, I just push the changes back to XXX. If I > don't want the changes I can just delete the directory YYY. > > Is this a bug? Is it a feature? What's the proper fossil technique? It is a feature. In hg, the working directory and the repository all all wrapped together as one. With fossil they are distinct. If you want a separate copy of the repository, you'll need to clone it using the "fossil clone" command. Then check out the new working directory from the clone. Also: be sure to turn off autosync in the clone or it will try to automatically push its changes back to the original. > > > Fossil Settings > --------------- > Fossil has a great web based UI to adjust fossil settings. You can > also > adjust some fossil settings via the command line using "fossil set". > But I can't seem to locate the setting available through "fossil > set" in > the web UI. Are they there and I just can't find them, or are they > missing for a reason? Not everything in the command-line is duplicated in the web interface, and vice versa. Fossil is a work in progress. If you see a feature you would like in the web interface, grab a copy of the fossil source code and add it! > > > Thanks, > Erik > > > _______________________________________________ > fossil-users mailing list > [email protected] > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users D. Richard Hipp [email protected] _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
