On 9/21/2015 10:32 AM, Warren Young wrote:
On Sep 21, 2015, at 10:21 AM, Ron Aaron <[email protected]> wrote:
I was hoping in vain for an easier solution.
How would you imagine Fossil would support this, which would end up being
easier?
What about the Bundle mechanism?
IIRC, it was intended to provide capability to Git pull requests in a
fossilish way. So as I understand it, it can be used to migrate changes
from one repository to another, with a fair bit of control over what
moves at both the sending and receiving end.
You would begin work on your paid feature in a clone constructed to have
only the amount of history you want to reveal. I suspect a bundle could
be used to populate an empty repo to begin that.
You would use bundles to package changes from the main repo to apply to
the clone, and vice-versa.
I'm not sure if the clone needs to share any features at all with the
original, I haven't personally had reason to use bundles yet.
--
Ross Berteig [email protected]
Cheshire Engineering Corp. http://www.CheshireEng.com/
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
