A proposal, to extend MercurialRepository/GitRepository to have clone point we clone at, and also disable default update to workingcopy after clone, i think it's waste of diskspace, and make the whole operation longer. I know that You can specify clone_point, and update option to mercurials api. Also i seen that clone_point is possible for git, and also --no-checkout options is an equivalent of no update in mercurial.
One option is to make
{{{
!python
def init(self, repo_path, create=False, baseui=None, clone_url=None,
clone_point=None):
}}}
and another
{{{
!python
def init(self, repo_path, create=False, baseui=None,
{'clone_url':None,'clone_point':None,'update':False}):
}}}
What do You think Lukasz ?
Reference: https://bitbucket.org/marcinkuzminski/vcs/issues/29/
A proposal, to extend MercurialRepository/GitRepository to have clone point we clone at, and also disable default update to workingcopy after clone, i think it's waste of diskspace, and make the whole operation longer. I know that You can specify clone_point, and update option to mercurials api. Also i seen that clone_point is possible for git, and also
--no-checkoutoptions is an equivalent of no update in mercurial.One option is to make
{{{
!python
def init(self, repo_path, create=False, baseui=None, clone_url=None,
clone_point=None):
}}}
and another
{{{
!python
def init(self, repo_path, create=False, baseui=None,
{'clone_url':None,'clone_point':None,'update':False}):
}}}
What do You think Lukasz ?
Reference: https://bitbucket.org/marcinkuzminski/vcs/issues/29/