-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Fossil's all-in-one idea is starting to grow on me. Last night I read about branching and tagging, which sparked a thought on how to do a multi-project setup. I'f tested it and it works superficially, but I'm wondering if there's something inherent in what I'm doing that makes it a bad idea.
I created and opened an empty repository. Next, I created branches called project_1 and project_2 based off of the empty commit. I could then successfully open/checkout project_1 and project_2. I then committed different files to each, each having different names and contents. After having done so, I could open projects based ontheir branch name and see the respective contents of that project. The only immediately obvious gotcha is that opening with no version seems to give you the project with the latest commit, but in this multi-project case I'm fine with undefined behavior for people not following directions on how to use the tools. :) It also then occurs to me that someone can still commit to the trunk branch. Is it possible to delete trunk, or is that what closed tags are for? Thinking the latter, but I want to confirm my understanding. Other than tracking multiple projects in a single wiki/timeline not working for some use cases, is there anything that makes such a solution a bad idea? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkyA+c4ACgkQIaMjFWMehWI0wwCdFhTX2m/9M6IUjmzOy9NhBPod Z8oAn03SGpNCx14vwGp0OYdwe26J+wid =G3SU -----END PGP SIGNATURE----- _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
