[GitHub] lucene-solr pull request #:

Previous Topic Next Topic
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
Report Content as Inappropriate

[GitHub] lucene-solr pull request #:

Github user nguyenhoan commented on the pull request:

    In lucene/join/src/test/org/apache/lucene/search/join/TestBlockJoin.java:
    In lucene/join/src/test/org/apache/lucene/search/join/TestBlockJoin.java on line 1082:
    Hi @mvgsoftware
    We are a team of researchers from Iowa State, The University of Texs at Dallas and Oregon State University, USA. We are investigating common/repeated code changes.
    We have four short questions regarding the change in the image below which is part of this commit.
    Q1- Is the change at these lines similar to another change from before? (yes, no, not sure)
    Q2- Can you briefly describe the change and why you made it? (for example, checking parameter before calling the method to avoid a Null Pointer Exception)
    Q3- Can you give it a name? (for example, Null Check)
    Q4- Would you like to have this change automated by a tool? (Yes, No, Already automated)
    The data collected from the answers will never be associated with you or your project. Our questions are about recurring code changes from the developer community, not about personal information. All the data is merged across recurring changes from GitHub repositories. We will publish aggregated data from the trends of the whole community.
    We have a long tradition of developing refactoring tools and contributing them freely to the Eclipse, Netbeans, Android Studio under their respective FLOSS licenses. For example, look at some of our recently released refactoring tools: http://refactoring.info/tools/ 
    Thank you,
    Hoan Nguyen https://sites.google.com/site/nguyenanhhoan/
    Michael Hilton http://web.engr.oregonstate.edu/~hiltonm/
    Tien Nguyen http://www.utdallas.edu/~tien.n.nguyen/
    Danny Dig http://eecs.oregonstate.edu/people/dig-danny

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [hidden email] or file a JIRA ticket
with INFRA.

To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]