dmidecode-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [dmidecode] contribute to dmidecode for spec 2.8 and 3.0


From: sai
Subject: Re: [dmidecode] contribute to dmidecode for spec 2.8 and 3.0
Date: Wed, 26 Aug 2015 11:23:01 -0600
User-agent: Roundcube Webmail/1.0.5


Hi Jean,

Yes, thanks for the information and the ticket about Contribution information. I think I spoke too soon :). I was using dmidecode-2.12 via buildroot and thought that was on the HEAD of the source tree. I realized after I did a git clone of the code that all that I needed was already there.

I found a typo that the 2.8 specification corrected that I didn't see in the code so I'll submit that :).

I was also wondering why aren't the names such as '(7.5.2) Processor Family' are not the same as those in the specification ?

--
Sai



On 2015-08-26 03:21, Jean Delvare wrote:
Hi Sai,

Le Friday 21 August 2015 à 17:01 +0000, address@hidden a écrit :
I am in the process of modifying dmidecode 2.12 to add support for
SMBIOS spec 2.8 and following which I plan to add support for 3.0 as
well.

dmidecode already supports SMBIOS 2.8 and 3.0...

I didn't find a CONTRIBUTION file in the CVS source tree or a link on
the project page.

... which you should have figured out already if you checked out the CVS
version of the code.

The README file contains the following note:

If you want to help with the development of dmidecode, please consider
joining the dmidecode-devel discussion list:
  http://lists.nongnu.org/mailman/listinfo/dmidecode-devel

But I agree the contribution process could be better documented. I've
created a support ticket for that:

https://savannah.nongnu.org/support/index.php?108872

Can anyone please let me know what is the process for contributing
code ? Where can I submit my changes for review ?

Posting patches to this mailing list is the appropriate process. For
features which aren't already implemented, that is ;-)

Note: the CVS tree is frozen now as we just moved to git.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]