kriegaex commented on PR #131: URL: https://github.com/apache/maven-enforcer/pull/131#issuecomment-1138638208
No, I do not understand. Rebasing by yourself takes much less time than having this conversation with me. And even if I do rebase, you still need to verify that the test does the right thing and would fail when run against an **older** version of the code before the problem the test is reproducing was fixed. I have extensively described the situation, if you follow the links to Jira and from there to the original issue. Furthermore, there might be 100+ projects maintained by the Maven team or by Apache in general. But every time I am trying to contribute a fix, a test or a feature to any of them, I am facing unnecessary bureaucracy, eating not just my own time (I am a volunteer doing work for free here, too) but the committers' time as well. You are not doing me a favour by accepting my PR, I am doing you one by providing it. So please, treat contributions with the same respect you repsect from contributors. Oh, and by the way:  So what is the actual problem? There is not even a merge conflict which I could solve for you, saving you a few minutes' time, by rebasing. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
