Skip to content
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

Add ol.structs.RBush#isEmpty #1331

Merged
merged 1 commit into from
Dec 4, 2013
Merged

Conversation

twpayne
Copy link
Contributor

@twpayne twpayne commented Dec 4, 2013

No description provided.

twpayne added a commit that referenced this pull request Dec 4, 2013
@twpayne twpayne merged commit bcda3aa into openlayers:master Dec 4, 2013
@twpayne twpayne deleted the rbush-is-empty branch December 4, 2013 14:26
@twpayne
Copy link
Contributor Author

twpayne commented Dec 4, 2013

Trivial enough to merge immediately.

@ahocevar
Copy link
Member

ahocevar commented Dec 4, 2013

Trivial enough to merge immediately.

😕

@twpayne
Copy link
Contributor Author

twpayne commented Dec 4, 2013

Sorry, I don't understand your response @ahocevar. Could you give more detail in words?

@bartvde
Copy link
Member

bartvde commented Dec 4, 2013

See the guidelines here: "Any changes to master, aside from improvements to tests and documentation, shall first be submitted for review as a github pull request."

http://trac.osgeo.org/openlayers/wiki/HowToContribute

@bartvde
Copy link
Member

bartvde commented Dec 4, 2013

I must admit that I thought examples were also not requiring review (which is why I merged an example a couple of days ago actually without review), but apparently only tests and documentation are exempted from review.

@ahocevar
Copy link
Member

ahocevar commented Dec 4, 2013

@twpayne While I agree that this specific pull request was trivial, I still think that a good community citizen should not judge their own pull requests trivial or non trivial. If you do this, others might start doing it too, and it is my educated guess that you'll be one of the first to dislike such behaviour.

@twpayne
Copy link
Contributor Author

twpayne commented Dec 4, 2013

See the guidelines here: "Any changes to master, aside from improvements to tests and documentation, shall first be submitted for review as a github pull request."

@bartvde, perhaps you can explain this to @ahocevar (refs #1280 #1246 #1095 ...).

@bartvde
Copy link
Member

bartvde commented Dec 4, 2013

this is not really fair @twpayne

#1246 was fixing an immediate issue with Travis
#1095 is improvement to tests so exempted

#1280 is an example only, no code, strictly speaking needs review though but maybe we should change this

@ahocevar
Copy link
Member

ahocevar commented Dec 4, 2013

I also was under the impression that examples can be merged without review, so I apologize for #1280. @bartvde I think it cannot hurt to demand reviews for examples also, so I'll stop merging example code without review from now on.

@bartvde
Copy link
Member

bartvde commented Dec 4, 2013

@ahocevar agreed on the examples. I'll also remember from now on not to merge an example without review.

Let's all just stick to the rules and not make exceptions, that's the easiest.

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

Successfully merging this pull request may close these issues.

None yet

3 participants