Hi, Is there a recommended workflow for Fossil to achieve the equivalent of SVN's "vendor branches"?
I have a project libB that is a fork of an open source library libA. libA is typically released as occasional tarballs. Some of my changes are bug fixes to libA (which I would like to be able to isolate and contribute back upstream), which others are new functionality that forms libB. In SVN, CVS, VSS, etc. I would have 3 directories: libA, myLibA (branch from libA), and libB (branch from libB). If I use branches in Fossil in the obvious manner, then I can only see one of these three code trees at a time, which makes diffs awkward (amongst other things). I seem to spend a lot of time keeping the branch structure in my head when navigating the code trees, rather than being able to see it on disk. Any advice welcome :) Regards, Twylite _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
