X-Sylpheed-Account-Id:1
S:andy.sharp@onstor.com
SCF:#mh/Mailbox/sent
X-Sylpheed-Sign:0
X-Sylpheed-Encrypt:0
X-Sylpheed-Privacy-System:
X-Sylpheed-End-Special-Headers: 1
Date: Sat, 29 Dec 2007 11:24:11 -0800
From: Andrew Sharp <andy.sharp@onstor.com>
To: Maxim Kozlovsky <maxim.kozlovsky@onstor.com>, Larry Scheer
 <larry.scheer@onstor.com>
Subject: questions about cmd_flash.c and children
Message-ID: <20071229112411.107dcb80@ripper.onstor.net>
Organization: Onstor
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

I have some questions about nfx-tree/code/ssc-nfxsh/cmd_flash.c and
children cmd_flash-openbsd.c and cmd_flash-linux.c.  The two children
were merely 'added' on April 19th, not integrated from current
cmd_flash.c, and appear to be literally months older, like 4 months
older, than the current cmd_flash.c.  How could that have been?

It looks like Larry did a 'merge' from the cmd_flash.c in main branch
to cmd_flash.c in cougar on April 17th, but that change was not
reflected in the children for some reason. Then on May 4th, Larry did
another merge from main/ branch cmd_flash.c, this time to
cmd_flash-openbsd.c only, leaving cmd_flash-linux.c untouched, and
therefore completely incompatible out of date, obviously.  It looks
like cmd_flash-openbsd.c has been maintained since, but
cmd_flash-linux.c, being completely out of date, has had a few
non-functional modifications since.

What gives?  Why weren't the children created from the latest version
of cmd_flash.c?  Why wasn't cmd_flash-linux.c updated when the openbsd
version was?  This has left the linux version unmaintained for six
months.