|
I'm looking for a good way to handle the following scenario:
I have a main repo with ongoing development. Now I have a customer who wants a customized version of my product.
The obvious thing is to simply add a branch for the customer on my main repo. But the customer wants access, and he should only get access to his branch of the repo; and similarly, it may be that he doesn't want to allow all my repo users access to his additions.
So the next obvious solution is to fork the repo. But now I have repo and repo-custom, where the latter contains just the 'branch' of the customer.
What I'm looking to do is have the ability to do merges using fossil, between the two repos. Obviously I can use a tool like 'Beyond Compare' but using fossil makes it so much easier. If it's possible, that is...
Anyone doing something similar?
--
Best regards,
Ron Aaron +1 425.296.0766 +972 52.652.5543 |
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
