Ralf, Apologies for the delay in responding to this. I believe it would be preferable to have fewer commits on the proviso that each commit has patches that have a logical relationship to each other. If the patches are not really related they are best done as stand-alone.
- John T. -----Original Message----- From: crowbar-bounces On Behalf Of Ralf Haferkamp Sent: Thursday, May 02, 2013 3:06 AM To: crowbar Subject: [Crowbar] Pull request review for SUSE support in Pebbles Hi, as you might have noticed we started forward-porting some of the patches for SUSE support from our essex-hack branches to the pebbles branches. For that I submitted already some pull requests. Currently: https://github.com/crowbar/barclamp-crowbar/pull/510 and https://github.com/crowbar/crowbar/pull/1793 Currently the plan is to submit pull requests in smaller chunks to allow for easier review. Another option would be to try to submit everything at once (or at least in very few chunks). I am wondering what the preferred solution is for this? Excluding the openstack barclamps we are talking about 80-100 commits for the crowbar and provsioner barclamps and much fewer commits (1-15) on each of the other barclamps ( network, dns, deployer, ntp, logging, ipmi and test) -- regards, Ralf _______________________________________________ Crowbar mailing list [email protected] https://lists.us.dell.com/mailman/listinfo/crowbar For more information: http://crowbar.github.com/ _______________________________________________ Crowbar mailing list [email protected] https://lists.us.dell.com/mailman/listinfo/crowbar For more information: http://crowbar.github.com/
