From owner-freebsd-bugs Wed Apr 22 07:09:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA18118 for freebsd-bugs-outgoing; Wed, 22 Apr 1998 07:09:31 -0700 (PDT) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA18110 for ; Wed, 22 Apr 1998 14:09:28 GMT (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id QAA03572; Wed, 22 Apr 1998 16:08:56 +0200 (CEST) To: Adam David cc: freebsd-bugs@FreeBSD.ORG Subject: Re: bin/6364 In-reply-to: Your message of "Wed, 22 Apr 1998 13:52:51 -0000." <199804221352.NAA23027@veda.is> Date: Wed, 22 Apr 1998 16:08:56 +0200 Message-ID: <3570.893254136@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <199804221352.NAA23027@veda.is>, Adam David writes: >> Synopsis: cpio complains about file flags >> >> State-Changed-From-To: open-closed >> State-Changed-By: phk >> State-Changed-When: Tue Apr 21 23:29:52 PDT 1998 >> State-Changed-Why: >> from what you say it pprobably should say so. > >this is a feature? No, that is how schg works, isn't it ? I pressume from the rather sparse data in your PR that you had schg set on some files on the ufs tree... If not please provide some more info... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "Drink MONO-tonic, it goes down but it will NEVER come back up!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message