From owner-freebsd-current Thu Apr 27 17:47:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id DCED837BE24 for ; Thu, 27 Apr 2000 17:47:48 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id UAA50288; Thu, 27 Apr 2000 20:47:42 -0400 (EDT) (envelope-from wollman) Date: Thu, 27 Apr 2000 20:47:42 -0400 (EDT) From: Garrett Wollman Message-Id: <200004280047.UAA50288@khavrinen.lcs.mit.edu> To: Peter Jeremy Cc: current@FreeBSD.ORG Subject: Re: asm_pci.h,v Holy cow! In-Reply-To: <00Apr28.093740est.115303@border.alcanet.com.au> References: <200004241536.LAA33905@khavrinen.lcs.mit.edu> <200004241726.NAA34251@khavrinen.lcs.mit.edu> <00Apr28.093740est.115303@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > How do you suggest such files get distributed? cvsup and/or rsync. This does leave CTM-users the odd men out.... > As Matt pointed out, CVS provides us with a good mechanism for > ensuring that I can identify what version of the firmware I am using > - and be reasonably certain it matches the code that Matt (or > whoever) validated. So would simply naming the files by version. This works because most if not all of our drivers use firmware from another vendor with its own version-numbering scheme. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message