I don't mind.. I just didn't know if I could... I'm not associated
with the project at all on SF so I didn't know if anyone could just
dump stuff on there or not. Plus, I kind of wanted to introduce
myself first before throwing down a bunch of code...
I'll start working on this.. I did all the pa
Jim, all said.
Dan, if you don't want to waste("waste") time with tracker, then dump
patches to mailing list/some HTTP/wherever and somebody, I, will
create tickets.
Thanks,
Z.
On Mon, Mar 18, 2013 at 9:40 PM, Jim Mankovich wrote:
> Dan,
>
> Creating a on or more tracker request for the changes
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 s
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
