AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20070403170049.7272d84b@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<larry.scheer@onstor.com>,<tim.gardner@onstor.com>,<maxim.kozlovsky@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
X-Sylpheed-End-Special-Headers: 1
Date: Tue, 3 Apr 2007 17:01:00 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: Larry Scheer <larry.scheer@onstor.com>
Cc: Tim Gardner <tim.gardner@onstor.com>, Maxim Kozlovsky
 <maxim.kozlovsky@onstor.com>
Subject: documentation of changes to cougar branch
Message-ID: <20070403170100.5cd12df5@ripper.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Hi Larry,

You've checked in a number of changes and additions to the cougar
branch without review.  Consequently, nobody knows how the stuff you
checked in works, where it lives, what the operating theory is ... etc.

Could you write a _brief_ design document that captures all this
information?  Where things are checked in, how the makefiles work, and
so on?  Feel free to use whatever format makes you happy: wiki,
open-document-format, or plain text file.  ~:^)

That would be a big help.  I'm looking for somewhere to check in my
kernel bits, but I really don't know where to start.  This will help me
there but also in other things.

Thanks,

a
