[devel] [PATCH 0 of 1] Review Request for IMMTOOLS: fix RDN value with a DN of an associated object in immcfg [#702]

[Zoran M. <zor...@er...>]

Summary: IMMTOOLS: fix RDN value with a DN of an associated object in immcfg [#702]
Review request for Trac Ticket(s): 702
Peer Reviewer(s): Neelakanta
Pull request to: Zoran
Affected branch(es): opensaf-4.2.x, opensaf-4.3.x, default(4.4)
Development branch: default(4.4)

--------------------------------
Impacted area       Impact y/n
--------------------------------
 Docs                    n
 Build system            n
 RPM/packaging           n
 Configuration files     n
 Startup scripts         n
 SAF services            y
 OpenSAF services        n
 Core libraries          n
 Samples                 n
 Tests                   n
 Other                   n


Comments (indicate scope for each "y" above):
---------------------------------------------

changeset c1d4723658c97fd09efae45e4ac1efe2dcfc1ae7
Author:	Zoran Milinkovic <zor...@er...>
Date:	Thu, 02 Jan 2014 13:15:55 +0100

	IMMTOOLS: fix RDN value with a DN of an associated object in immcfg [#702]

	Fix RDN value with a DN of an associated object when a new object is created
	by immcfg.


Complete diffstat:
------------------
 osaf/tools/safimm/immcfg/imm_cfg.c |  36 +++++++++++++++++++-----------------
 1 files changed, 19 insertions(+), 17 deletions(-)


Testing Commands:
-----------------
Example:
immcfg -c TestClass 'id=testid=1\,testid=5'


Testing, Expected Results:
--------------------------
Create a test class.
Using immcfg, create an object of the new created class with a DN that has only object RDN, without parent DN.
With the provided patch, immcfg should not crash.


Conditions of Submission:
-------------------------
Ack from Neelakanta


Arch      Built     Started    Linux distro
-------------------------------------------
mips        n          n
mips64      n          n
x86         n          n
x86_64      n          n
powerpc     n          n
powerpc64   n          n


Reviewer Checklist:
-------------------
[Submitters: make sure that your review doesn't trigger any checkmarks!]


Your checkin has not passed review because (see checked entries):

___ Your RR template is generally incomplete; it has too many blank entries
    that need proper data filled in.

___ You have failed to nominate the proper persons for review and push.

___ Your patches do not have proper short+long header

___ You have grammar/spelling in your header that is unacceptable.

___ You have exceeded a sensible line length in your headers/comments/text.

___ You have failed to put in a proper Trac Ticket # into your commits.

___ You have incorrectly put/left internal data in your comments/files
    (i.e. internal bug tracking tool IDs, product names etc)

___ You have not given any evidence of testing beyond basic build tests.
    Demonstrate some level of runtime or other sanity testing.

___ You have ^M present in some of your files. These have to be removed.

___ You have needlessly changed whitespace or added whitespace crimes
    like trailing spaces, or spaces before tabs.

___ You have mixed real technical changes with whitespace and other
    cosmetic code cleanup changes. These have to be separate commits.

___ You need to refactor your submission into logical chunks; there is
    too much content into a single commit.

___ You have extraneous garbage in your review (merge commits etc)

___ You have giant attachments which should never have been sent;
    Instead you should place your content in a public tree to be pulled.

___ You have too many commits attached to an e-mail; resend as threaded
    commits, or place in a public tree for a pull.

___ You have resent this content multiple times without a clear indication
    of what has changed between each re-send.

___ You have failed to adequately and individually address all of the
    comments and change requests that were proposed in the initial review.

___ You have a misconfigured ~/.hgrc file (i.e. username, email etc)

___ Your computer have a badly configured date and time; confusing the
    the threaded patch review.

___ Your changes affect IPC mechanism, and you don't present any results
    for in-service upgradability test.

___ Your changes affect user manual and documentation, your patch series
    do not contain the patch that updates the Doxygen manual.