From owner-freebsd-current@FreeBSD.ORG Sun Jul 24 06:16:07 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1B67C16A41F; Sun, 24 Jul 2005 06:16:07 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF17B43D46; Sun, 24 Jul 2005 06:16:04 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from niksun.com (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.1/8.13.1) with ESMTP id j6O6IAIk099972; Sun, 24 Jul 2005 02:18:10 -0400 (EDT) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: Doug Barton Date: Sun, 24 Jul 2005 02:15:33 -0400 User-Agent: KMail/1.6.2 References: <200507220549.j6M5nfhO059858@repoman.freebsd.org> <47d0403c05072218491c78e2e9@mail.gmail.com> <42E29157.3090908@FreeBSD.org> In-Reply-To: <42E29157.3090908@FreeBSD.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200507240215.44476.jkim@FreeBSD.org> X-Virus-Scanned: ClamAV 0.85.1/989/Fri Jul 22 17:27:30 2005 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: freebsd-current@FreeBSD.org, Ben Kaduk Subject: Re: cvs commit: src/usr.sbin/ndiscvt ndisgen.sh X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Jul 2005 06:16:07 -0000 On Saturday 23 July 2005 02:49 pm, Doug Barton wrote: > Ben Kaduk wrote: > > I know it's bad form to reply to myself, > > It's not actually, that's a myth that needs to be busted. :) This > is especially true when you have found the right answer, and can > save others time investigating the problem. > > > but this patch seems to allow > > ndisgen to recognize my .inf file: > > Thanks! I noticed a similar problem with my own INF file, and in my > case it turned out that the various lines it was searching for did > not occur in the first column, but were indented. Removing the ^ in > all places it occurred fixed this for me, so I've committed the > fix. Sorry, I didn't know indentation was supported. :-( Thanks for the fix and a new feature! Jung-uk Kim > Good hunting, > > Doug