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

testing: use repo path that does not need updating when import path changes #33

Merged
merged 1 commit into from Aug 1, 2014

Conversation

rogpeppe
Copy link
Contributor

@rogpeppe rogpeppe commented Aug 1, 2014

It was easy to forget to change the package path when updating the gopkg.in version,
and govers doesn't know enough to be able to warn about it, unlike import paths.

@themue
Copy link
Contributor

themue commented Aug 1, 2014

Interesting way, LGTM.

@urosj
Copy link
Contributor

urosj commented Aug 1, 2014

👍

rogpeppe added a commit that referenced this pull request Aug 1, 2014
testing: use repo path that does not need updating when import path changes
@rogpeppe rogpeppe merged commit 2be040b into juju:v3 Aug 1, 2014
@jrwren
Copy link
Contributor

jrwren commented Aug 1, 2014

LGTM but what is the gain? isn't it just 2 ways to do the same thing?

jrwren pushed a commit to jrwren/charm that referenced this pull request Aug 6, 2014
Update to gopkg.in/mgo.v2 repository
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

Successfully merging this pull request may close these issues.

None yet

4 participants