Dan, Creating a on or more tracker request for the changes would be best. Simply explain the issue and how the patch resolves it along with the patch itself. It would be best to patch against the current TOB ipmitool version. You can then request a code review on the ipmitool-devel alias and simply reference the tracker request.
This is generally what I have done in the past for fairly straight forward changes. Any one else want to chime in on this? Thanks for you interest in helping, Jim -- Jim Mankovich | jm...@hp.com -- On 3/18/2013 1:34 PM, Dan Gora wrote: > Hi All, > > I've been working on fixing several issues with ipmitool and I've got > about 30 patches to fix numerous issues, but I'm not really sure what > the best way is to contribute the patches back upstream. > > Should I just post the patches here to the mailing list a-la the > kernel-devel list? > > Do they have to be in some kind of series notation? > > Do you require signed-off by lines? > > Are there any kind of patch prep scripts that need to be run on them first? > > Do I need to do anything on sourceforge? Create trackers or something? > > thanks for any info. > > dan ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar _______________________________________________ Ipmitool-devel mailing list Ipmitool-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
