Skip to content

added support for specifying specific branch/tag/revision while installing#604

Merged
evieluvsrainbows merged 1 commit intoVundleVim:masterfrom
wolph:master
Jul 9, 2015
Merged

added support for specifying specific branch/tag/revision while installing#604
evieluvsrainbows merged 1 commit intoVundleVim:masterfrom
wolph:master

Conversation

@wolph
Copy link
Contributor

@wolph wolph commented May 28, 2015

This fixes #35

Now it's possible to specify a tag, branch or revision using @...:

Example: Plugin 'WoLpH/nerdtree@patch-1'

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

'git reset --hard origin/'.a:bundle.revision,
I think this is what you want (which was done in line 396 in a wrong way) ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That would probably work too. In what way is line 396 wrong? I've been using this fork for a while without any issues

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's usual that the wrong codes "works", but this doesn't means it's right.

What if the a:bundle.revision branch uses a new submodule ?

@evieluvsrainbows
Copy link
Contributor

Merging, since this seems like a pretty cool feature.

@evieluvsrainbows
Copy link
Contributor

I'll fix it afterwards.

evieluvsrainbows pushed a commit that referenced this pull request Jul 9, 2015
added support for specifying specific branch/tag/revision while installing
@evieluvsrainbows evieluvsrainbows merged commit e31d302 into VundleVim:master Jul 9, 2015
@gmarik
Copy link
Contributor

gmarik commented Jul 9, 2015

Merging, since this seems like a pretty cool feature.

@KamranMackey

  1. have anyone other than author tested it?
  2. is it backward compatible?

Before merging require atleast 2 confirmation from other team members

/cc @VundleVim/team

@evieluvsrainbows
Copy link
Contributor

@gmarik Oh yeah, crap. Forgot about that. Sorry.

@gmarik
Copy link
Contributor

gmarik commented Jul 9, 2015

@KamranMackey while it's not too late i'd suggest hard resetting it back to where it was before. Otherwise you'll get flooded with support issues very soon…

@gmarik
Copy link
Contributor

gmarik commented Jul 9, 2015

@KamranMackey let's figured out process first before getting to merging code. Ok?

@evieluvsrainbows
Copy link
Contributor

@gmarik created a PR that reverts #616, since that's the one that might've broken Vundle. I doubt this one did.

@luochen1990
Copy link
Contributor

@KamranMackey intersting...

@wolph
Copy link
Contributor Author

wolph commented Jul 9, 2015

@gmarik @KamranMackey Perhaps it's time to look at Travis tests? Doesn't have to be fully covering initially but some automated tests might help with accepting pull requests.

@silfverstrom
Copy link
Member

@wolph +1 on adding some automated test-coverage.

@gmarik
Copy link
Contributor

gmarik commented Jul 9, 2015

👍 if anyone want's to figure out testing process…

@gmarik
Copy link
Contributor

gmarik commented Jul 9, 2015

@silfverstrom create separate issues for testing?

@silfverstrom
Copy link
Member

@gmarik yeah I'll add a new issue.

@fearphage
Copy link

Is any of this ever coming to master?

@ryanoasis
Copy link
Member

@fearphage Good question. I tried getting a next release branch up but we had some issues. I still want to help release the next version but really paranoid about breaking vundle (considering how many vim users use it still).

I have been too busy but hopefully in a few weeks I can contribute more. I have only been merging the most trivial of PRs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Support for locking onto a Tag or Branch

7 participants