New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
defunkt/gist is broken, ConradIrwin/jist is better ∴ this should be a fork. #13
Comments
Making it a fork of defunkt/gist would help the other way around — people would go there from here... |
Not a chance. Why would they go from something that's good to something that's buggy, incomplete, and unmaintained? The reason I made this ticket is because a user on #github was saying the "gist" repo is unmaintained, but it's not clear which of the forks to use. Having this one hanging on the tree with a steady little Pac-man line of commits would advertise it. |
@issue_spam += 1 |
Yeeeeah so I'm mildly inclined to just pull jist back into gist and cut a release. @ConradIrwin, how do you feel about that? |
@indirect: That's good by me. There are some minor differences in the command line parsing, but nothing massively different I don't think. |
Oh, authentication is completely different. |
(Honestly I would just add you and @rking to the gist repo and gem, but I don't have admin, only commit. Sorry. :|) |
Yeah, your authentication seems much less horrifyingly awful. FWIW. |
(No worries — thanks for fixing up gist :). |
@indirect since you have commit, how about a note at the top of the 'gist' README pointing to this project? |
As soon as I get the chance. Medium-term, I'm going to merge jist in. On Jan 21, 2013, at 8:15 AM, John Goulah notifications@github.com wrote:
|
People can't get to here from defunkt/gist.
My proposal is that you move the repo, fork gist, then re-import the current code/history.
Down with abandonware!
The text was updated successfully, but these errors were encountered: