-
Notifications
You must be signed in to change notification settings - Fork 37
Forked Due to Apparent Loss of Maintainer #41
Comments
I've also got a fork at brbsix/vagrant-bash-completion with some significant updates. |
Argh. Would have been nice if you'd announced this here before I'd spent an hour forking and pulling in all the other changes and the like. This issue is, of course, this repo is the top hit for "vagrant bash completion" on both Google and DuckDuckGo, soltysh and ddarbyson come in on the top page of each respectively and Anyway, now that people know about this, do you want to pull in to your repo the changes I have that you don't ( |
Apologies. I suppose it's not particularly convenient to find, but doesn't my fork show up at the top of https://github.com/kura/vagrant-bash-completion/network? I just added |
Ah, that's a good (if not obvious) way of searching. Anyway, good stuff. I've just updated and done a quick test of the current head of your master branch and everything seems ok. So I'll use that from this point on and kill my own fork. Thanks for the quick response! |
@C-J-S https://github.com/c-j-s/vagrant-bash-completion throws |
@yermulnik: Right, as one might expect if one reads the message immediately above yours. :-) But good point; I've edited the initial message in this thread to point directly to @brbsix's repo. |
The maintainer of this repo appears to have vanished (I tried to e-mail him but his domain has expired). Maintenance has now been taken over by
brbsix
in the fork at brbsix/vagrant-bash-completion, with all PRs as of this date incorporated.(The previous fork at c-j-s/vagrant-bash-completion has been removed.)
The text was updated successfully, but these errors were encountered: