Skip to content
This repository has been archived by the owner on Nov 17, 2017. It is now read-only.

Forked Due to Apparent Loss of Maintainer #41

Open
0cjs opened this issue Mar 22, 2017 · 6 comments
Open

Forked Due to Apparent Loss of Maintainer #41

0cjs opened this issue Mar 22, 2017 · 6 comments

Comments

@0cjs
Copy link

0cjs commented Mar 22, 2017

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.)

@brbsix
Copy link

brbsix commented Mar 22, 2017

I've also got a fork at brbsix/vagrant-bash-completion with some significant updates.

@0cjs
Copy link
Author

0cjs commented Mar 22, 2017

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
you don't appear at all, unfortunately. And keep in mind that forks don't appear in github searches either.

Anyway, now that people know about this, do you want to pull in to your repo the changes I have that you don't (box prune and the cygwin/mingw fix, from the looks of it) and then I can kill my fork?

@brbsix
Copy link

brbsix commented Mar 22, 2017

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 box prune support in brbsix@d6f10f0 (I had already implemented it a while ago but didn't commit until now). brbsix@9666a8a should address the cygwin/mingw issue.

@0cjs
Copy link
Author

0cjs commented Mar 22, 2017

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!

@yermulnik
Copy link

@0cjs
Copy link
Author

0cjs commented Mar 22, 2017

@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.

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

No branches or pull requests

3 participants