I personally think that "fossil open --empty" is a pretty good
strategy to keep multiple projects in the same repository.
Cheers.
- Vikrant
On 27 January 2015 at 03:57, Jim Kalafut <j...@kalafut.net> wrote:
> I have a number of small, disparate projects that I'm moving into
> Fossil. I've noticed that "fossil import --incremental" makes a new
> "Initial commit" for the tree being imported. This is actually good for
> what I'm doing. I've also discovered " fossil open --empty" which does
> the same thing for new work. I like the idea of these distinct starting
> points because these projects are distinct. But they're small, it's
> just me, and I also really like the idea of a single
> timeline/wiki/ticket system to cover it all, as opposed to a ton of tiny
> repos. I'm managing branches via a simple naming convention
> ("prj/branch"). If any of these projects grew substantially and had to
> become its own repo, I was thinking I could export that portion via
> "bundle export".
>
> All seems good, but I'm very new to Fossil so my question is: will this
> strategy come back to bite me?
>
>
> Thanks,
> Jim
> _______________________________________________
> 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
