Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VCS #54

Closed
schacki opened this issue Feb 15, 2012 · 1 comment
Closed

VCS #54

schacki opened this issue Feb 15, 2012 · 1 comment

Comments

@schacki
Copy link

schacki commented Feb 15, 2012

Should we add VCS features to cuisine or is that to high level? I was thinkg about:

  • vcs_pull or vcs_get (source,target,revision=None) ==> to pull from source to target directory and update target
  • vcs_push or vcs_put (source,target,revision=None) ==> to push from source to target and upate target
  • vcs_clone (source,target,revision=None) ==> to clone from source and create target and update target
  • vcs_ensure (source,target,revision=None) ==> to ensure that target matches source

and I personally would need it for git, and hg

Does this make sense?

@sebastien
Copy link
Owner

I think this might be a little overkill, but might be good as contrib module. Feel free to share and I'll include create a cuisine/contrib module.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants