Fix require lines. test.check > clojure.test.check #1

Closed
wants to merge 1 commit into
from

Projects

None yet

9 participants

@AeroNotix

No description provided.

@reiddraper
Member

I'm afraid test.check does not use pull-requests.

@reiddraper reiddraper closed this Mar 3, 2014
@AeroNotix

Bleghh, painful.

You know the error is there, I know the error is there. Let's just say it goes away and we forget about this PR.

@reiddraper
Member

I'm happy to fix the error, but you can read more about the patch process here.

@hyPiRion
Contributor
hyPiRion commented Mar 4, 2014

@AeroNotix, you could submit an issue over at http://dev.clojure.org/jira/browse/TCHECK – it's not necessary to have a CA for that.

@AeroNotix

JIRA is needless indirection, imho. I want no part in it.

@frenchy64
Member

Yeah, who needs a bug tracker anyway...

@AeroNotix

Eh, I don't want to get into a religious war over a typo.

@lprefontaine

+1, who needs to use software
in production with minimal
stability anyway ?

I do not care after all my code is
flawless on the first run.

I should be the only one allowed to
write code in this world.

Too bad you guys need JIRA to get
your code fixed afterward...

Luc P.

JIRA is a needless indirection, imho. I want no part in it.


Reply to this email directly or view it on GitHub:

#1 (comment)

Luc Prefontainelprefontaine@softaddicts.ca sent by ibisMail!

@AeroNotix

@lprefontaine Passive aggressiveness aside, if you think JIRA is needed for literally a couple of lines fixed in documentation then you need your head checking.

@ghost
ghost commented Mar 4, 2014

@AeroNotix You aren't going to win this.
Your betters at cognitect have decided github's issues and pull requests aren't a real issue tracking system, and if you can't see that you are stupid lazy and everything that is wrong with open source. They don't need you anyway.

@AeroNotix

@anonymousc0ward unsure if sarcasm or not.

@cemerick
Member
cemerick commented Mar 4, 2014

Please take this discussion elsewhere, thanks.

@lprefontaine

I agree, my code being the Holy
Grail,
I never write documentation,
my code conveys the Truth by itself.

Bad documentation needs to be maintained in sync
with releases of filthy code.

This is the plague most of you will carry for
the rest of your life hence the need
for the evil JIRA.

One day you may reach the ultimate
revelation though.

But obviously you need a few years
of production maintenance under your
belt :))))

Now if you think that my tone is
aggressive, well you need to consult.

Being ironic != aggressive :)

Irony may feel a bit like acid rain but
if you are so sensitive to it then ...
find some cover :)

Luc P,

@lprefontaine Passive aggressiveness aside, if you think JIRA is needed for literally a couple of lines fixed in documentation then you need your head checking.


Reply to this email directly or view it on GitHub:

#1 (comment)

Luc Prefontainelprefontaine@softaddicts.ca sent by ibisMail!

@AeroNotix

THIS CHANGE WAS A TWO LINE TYPO CHANGE YOU GODDAMN FAPPERS.

@michaelklishin

As much as I hate the paranoid and excluding Clojure contrib process…

@puredanger
Contributor

Everyone is aware that this process is conservative and at times cumbersome. We greatly appreciate the hundreds of people that have agreed to work within its confines to preserve the legal integrity of the language. This stuff really does matter and affects whether big companies are able to use the language and libraries without reservation. We are aware that some people don't like it.

Spamming nonsense and images into the email stream of the entire contrib commiter team (https://github.com/orgs/clojure/teams/contrib-commit) a) does not change anything and b) wastes the time and attention of all those people. Please, enough already.

@benatkin
benatkin commented Mar 5, 2014

This project uses GitHub for hosting its code but not its bug reports or code contributions (Pull Requests). Pull Requests made here are not part of the official project, but something outside of the official project that the project's owners have to clean up. It only exists because GitHub doesn't have an option to disable Pull Requests, like it does for issues. So please take note why this shouldn't be acted upon.

@AeroNotix

Christ almighty, LET IT GO.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment