On Sat, Sep 19, 2015 at 11:16 PM, Ron Aaron <[email protected]> wrote:
> 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, > [...] > 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. > Is there a reason you half to do development in the customer specific repository? My thought is that you do the development exclusively on a branch (or set of branched) on the main repo, then, as needed, create a bundle of just the customer's branch(es) and import that into the customer specific repo. That way, the customer will only have access to the files specific to it. See: "fossil help bundle" for more details.
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
