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

Install/update ignores changed remotes #48

Closed
dag opened this issue May 29, 2011 · 7 comments
Closed

Install/update ignores changed remotes #48

dag opened this issue May 29, 2011 · 7 comments
Assignees
Labels
Milestone

Comments

@dag
Copy link
Contributor

dag commented May 29, 2011

If I fork a bundle and change my configuration to use my fork, neither :BundleInstall or :BundleInstall! will pick it up - I would guess Vundle is just doing git pull without bothering about remotes.

The workaround of course is to delete the existing clone (or manually change the remotes) but it would be better if Vundle handled it for us.

@gmarik
Copy link
Contributor

gmarik commented May 29, 2011

+1 on this.
Changing remotes sounds like a cleanest solution...

@gmarik
Copy link
Contributor

gmarik commented Jul 24, 2011

Hey @dag.
pushed v branch which addresses this issue.
If you could find some time to test it would be awesome!
Thanks!

$ cd vundle && git pull && git checkout -b v origin/v

@mutewinter
Copy link

+1 to this, run into it all the time.

@Valloric
Copy link

Valloric commented Feb 1, 2013

I run into this all the time as well. Any chance of this getting fixed any time soon?

@vheon
Copy link
Contributor

vheon commented Aug 23, 2013

🆙 Any news?

@MarcWeber
Copy link

related to #367

@jdevera jdevera removed the feature label Apr 4, 2014
jdevera added a commit that referenced this issue Apr 15, 2014
If one had this plugin:

Plugin 'foo/bar'

And now switches to another one with the same name:

Plugin 'baz/bar'

Recognise this scenario and replace the old plugin with the new one,
rather than silently assuming they are the same.

Fixes #367 #48 #183 #400
jdevera added a commit that referenced this issue Apr 15, 2014
If one had this plugin:

Plugin 'foo/bar'

And now switches to another one with the same name:

Plugin 'baz/bar'

Recognise this scenario and replace the old plugin with the new one,
rather than silently assuming they are the same.

Fixes #367 #48 #183 #400
@jdevera
Copy link
Contributor

jdevera commented Apr 23, 2014

Fixed in f5a208b

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

No branches or pull requests

7 participants