You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
we made only update_after_clone, wich infact is a bad name, when now i think about it, it should be rather no_update,no_checkout to be more like command line option. But clone points are something not implemented. I do like it, and i think it's good value option. btw i'm more into keyworded arguments than dict
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/
The text was updated successfully, but these errors were encountered: