Merge lp://staging/~marcoceppi/charm-tools/vcs into lp://staging/~charmers/charm-tools/trunk
Proposed by
Marco Ceppi
Status: | Merged |
---|---|
Approved by: | Clint Byrum |
Approved revision: | 166 |
Merged at revision: | 157 |
Proposed branch: | lp://staging/~marcoceppi/charm-tools/vcs |
Merge into: | lp://staging/~charmers/charm-tools/trunk |
Diff against target: |
485 lines (+412/-7) 6 files modified
Makefile (+4/-1) helpers/bash/vcs.bash (+243/-0) helpers/sh/net.sh (+4/-5) tests/helpers/helpers.bash (+18/-0) tests/helpers/lib.sh (+3/-1) tests/helpers/test_vcs.bash (+140/-0) |
To merge this branch: | bzr merge lp://staging/~marcoceppi/charm-tools/vcs |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Clint Byrum (community) | Approve | ||
charmers | Pending | ||
Review via email: mp+121129@code.staging.launchpad.net |
Description of the change
I noticed so far two charms[1][3][2] take wild user input, supposedly a remote repository url, and takes action against that. This merge is designed to streamline the action of identifying what type of scm/vcs the remote source is and pull it down, or update a local repo from the remote source.
Demonstration of potential use cases: http://
[1]: http://
[2]: http://
[3]: http://
To post a comment you must log in.
I can has tests?! kthxbai!