Message-Id: <200504111744.j3BHiprd011008@delorie.com> Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com From: "Gary R. Van Sickle" To: Subject: RE: FDA-conform validation - any hints? Date: Mon, 11 Apr 2005 12:46:18 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit In-Reply-To: X-IsSubscribed: yes > -----Original Message----- > From: cygwin-owner@cygwin.com > [mailto:cygwin-owner@cygwin.com] On Behalf Of Jan Schormann > Sent: Monday, April 11, 2005 8:49 AM > To: cygwin@cygwin.com > Subject: FDA-conform validation - any hints? > > Hi all, > > my company develops medical devices, so we must fulfill the > FDA (U.S. Food & Drug Administration) regulations. > As we are using Cygwin in our software build chain > (especially for GNU make and bash), we need to explain what > makes us so confident. > > I've scanned the archives with no satisfying outcome, so ... > > Has anyone ever tried this before? > Do you have any hints? > > Thanks all! > Jan. > What Jim said, and also the FDA tends to be more concerned with test processes and results. -- Gary R. Van Sickle -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/