Github user runseb commented on the pull request:

    https://github.com/apache/cloudstack/pull/605#issuecomment-124565789
  
    @DaanHoogland ( cc/ @pdion891 @wido ), this one is not Java so I am 
comfortable reviewing it. The bottom line is that I don't review the 33 commits 
I review the final state of the PR. So why keep the crap that led to it ? it 
moves two files, create a new one, edits a markdown. 
    
    It's simple enough. I don't care if PL rewrites history of his own fork, I 
want clean history in our master. you might see this as necessary 
documentation, but I see it as unnecessary garbage that will pollute our 
source, I don't need a one commit that removes one comment in master.


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to