added support for specifying specific branch/tag/revision while installing#604
added support for specifying specific branch/tag/revision while installing#604evieluvsrainbows merged 1 commit intoVundleVim:masterfrom
Conversation
There was a problem hiding this comment.
'git reset --hard origin/'.a:bundle.revision,
I think this is what you want (which was done in line 396 in a wrong way) ?
There was a problem hiding this comment.
That would probably work too. In what way is line 396 wrong? I've been using this fork for a while without any issues
There was a problem hiding this comment.
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 ?
|
Merging, since this seems like a pretty cool feature. |
|
I'll fix it afterwards. |
added support for specifying specific branch/tag/revision while installing
@KamranMackey
Before merging require atleast 2 confirmation from other team members /cc @VundleVim/team |
|
@gmarik Oh yeah, crap. Forgot about that. Sorry. |
|
@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… |
|
@KamranMackey let's figured out process first before getting to merging code. Ok? |
|
@KamranMackey intersting... |
|
@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. |
|
@wolph +1 on adding some automated test-coverage. |
|
👍 if anyone want's to figure out testing process… |
|
@silfverstrom create separate issues for testing? |
|
@gmarik yeah I'll add a new issue. |
|
Is any of this ever coming to master? |
|
@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. |
This fixes #35
Now it's possible to specify a tag, branch or revision using
@...:Example:
Plugin 'WoLpH/nerdtree@patch-1'