I used to do the one big repo thing with subversion, but the main reason for
doing it that way was that it was a pain to setup a repo in the first place.
I have any number of JavaScript and php libraries that I use periodically in
different projects, but I don't use the same set each time. Until
i've also tried to get this to work, but fossil has some issues with checking
out multiple repositories to the same working folder/subfolder..
i haven't tried recently with the new ignore options, so it may be possible
now,
but I suspect it would take a bit of mucking around..
On 24/08/2010
Hi,
My current practice is to have a fossil repo per project. I've committed the
(cardinal) sin of duplicating shared files between projects. I want to fix
this.
Conceptually I'd like to have one huge repo for everything (individual projects
and all common files), and maintain working copies
3 matches
Mail list logo
