Skip to content
This repository has been archived by the owner on May 5, 2018. It is now read-only.

Closing this repo #577

Closed
nateabele opened this issue Mar 5, 2014 · 9 comments
Closed

Closing this repo #577

nateabele opened this issue Mar 5, 2014 · 9 comments
Labels

Comments

@nateabele
Copy link

This repo has been discontinued for months now, yet people still seem to occasionally be opening issues against it. I think it's time to tank it for good. /cc @ProLoser

@nateabele nateabele added the rfc label Mar 5, 2014
@ProLoser
Copy link
Member

ProLoser commented Mar 5, 2014

You think we should delete it?

@nateabele
Copy link
Author

It's too bad you can't archive it, but yeah, I think we should.

@ProLoser
Copy link
Member

ProLoser commented Mar 6, 2014

My concern (despite the stupidity) is that there are still resources and code references that until they are properly implemented I kind of don't want to lose (such as the pull request for ui-input)

@ProLoser
Copy link
Member

ProLoser commented Mar 9, 2014

So we need to remove the star and fork buttons.
On Mar 9, 2014 4:47 AM, "Diego" [email protected] wrote:

I think that the description and README of the repo should point to the
new repo
https://github.com/angular-ui/bootstrap

right now if you go to https://github.com/angular-ui/angular-ui/
you are told to go to http://angular-ui.github.com/
and if you click the star/fork icon, you go to
https://github.com/angular-ui/angular-ui/
so, you goes in a loop.

Reply to this email directly or view it on GitHubhttps://github.com//issues/577#issuecomment-37125118
.

@nateabele
Copy link
Author

the pull request for ui-input

Why not just pull it down and throw it in the angular-ui/ui-input repo?

@nateabele
Copy link
Author

Let me know if you need help with the git-fu for that.

@ProLoser
Copy link
Member

@nateabele uh yeah perhaps you could if you find time to do so. Off the top of my head i'm not sure of how to do this easily.

@nateabele
Copy link
Author

Cool, I'll try and take care of it in the next week or so.

@nateabele
Copy link
Author

@ProLoser To be clear, are you talking about #191?

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

No branches or pull requests

3 participants