-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have some situations where I find myself creating the same starter projects over and over. For instance, I'll create the same starter web app with similar database setup and coding style.
Were I doing this with Git, I'd start with a template repository, clone it and go. But I'm not sure this is possible with Fossil. My understanding is that Fossil creates a unique project ID such that it ensures syncs happen only between repositories of the same project. Is this accurate? If so, I wonder if a variant of "fossil new" might accept a second repository file or URL argument. This would copy all artifacts from the second repository into the first, then set a new project ID on the first repository. This would ensure that each new project has a distinct ID from the template, but still starts with the same artifacts. Or is there some other way to accomplish this goal? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk0K8AwACgkQIaMjFWMehWKbdACfZL2dpYkdcExmsBrq2COB/rDC uScAn1jwlg8weJmPAd5jjPKTE3dh4Pid =pyMJ -----END PGP SIGNATURE----- _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
