# Using subrepository

**URL:** https://discuss.tryton.org/t/using-subrepository/585
**Category:** Organisation
**Created:** [June 4, 2018, 2:43pm UTC](https://discuss.tryton.org/t/using-subrepository/585 "2018-06-04T14:43:21Z")
**Posts on this page:** 1
**Showing post:** 7

<div class="post-metadata">

### Author: ![ced](https://discuss-cdn.tryton.org/user_avatar/discuss.tryton.org/ced/32/1237_2.png) [@ced](https://discuss.tryton.org/u/ced)
#### Post date: [June 5, 2018, 9:28pm UTC](https://discuss.tryton.org/t/using-subrepository/585/7 "2018-06-05T21:28:13Z")

</div>

> [@pulkit](#):
>
> Due to lot of work going on to implement new features like partial clone, we are refactoring our API’s. I have hacked hgnested to support hg 4.6.

I understand that mercurial API’s need to evolve but this create too much work too follow the changes for a small extension like hgnested. Especially if standard alternative exists now that provides even more features.

> [@pulkit](#):
>
> Just FYI, subrepos are a feature of last resort

I know but I think it applies to our use case. hgnested is probably also a last resort extension.

> [@pulkit](#):
>
> and I won’t advise you to use it because in past there have been security issues because of subrepos

As far as I can see it was about using Git sub-repository. Indeed if Mercurial had no security issues, it will be suspicious. But having some, means that people are auditing it and so there are less issues. 😉  
Indeed we do not know if hgnested does not have security issues.

Have you another proposal?

---

_[View the full topic](https://discuss.tryton.org/t/using-subrepository/585)._