From owner-freebsd-bugs@FreeBSD.ORG Mon Dec 24 05:37:07 2007 Return-Path: Delivered-To: freebsd-bugs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 85E0216A537 for ; Mon, 24 Dec 2007 05:37:07 +0000 (UTC) (envelope-from qhwt+fbsd@les.ath.cx) Received: from les.ath.cx (15.61.205.61.west.global.alpha-net.ne.jp [61.205.61.15]) by mx1.freebsd.org (Postfix) with ESMTP id 3EF1813C468 for ; Mon, 24 Dec 2007 05:37:06 +0000 (UTC) (envelope-from qhwt+fbsd@les.ath.cx) Received: by les.ath.cx (Postfix, from userid 1000) id 0486A86618; Mon, 24 Dec 2007 14:37:04 +0900 (JST) Date: Mon, 24 Dec 2007 14:37:04 +0900 From: YONETANI Tomokazu To: freebsd-bugs@FreeBSD.org Message-ID: <20071224053704.GA28340@les.ath.cx> References: <200711051747.lA5HlP3l050792@freefall.freebsd.org> <20071205041822.GA67287@les.ath.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071205041822.GA67287@les.ath.cx> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: Subject: Re: bin/117831: csup is incompatible WRT handling unknown RCS keywords X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Dec 2007 05:37:07 -0000 On Wed, Dec 05, 2007 at 01:18:22PM +0900, YONETANI Tomokazu wrote: > On Mon, Nov 05, 2007 at 05:47:25PM +0000, remko@FreeBSD.org wrote: > > Over to maintainer. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=117831 > > Ok, obviously I overlooked at what's written in TODO file: > > BUGS: > : > - Add missing support for supfile keywords and add sanity checks for > some of them. Also, we're not supposed to choke on unknown keywords > to stay in line with CVSup, which just ignores them in order to > maintain compatibility with sup configuration files. > > so the author had already identified this problem far before I poked at him. > > IMHO, ignoring an unknown keyword(a newphrase) is just OK, as long as it > spews a warning. As many existing RCS/CVS tools are designed to behave > this way anyway, one won't (can't) add a newphrase which requires older > applications to upgrade and support it to operate on the new repository > properly. Apparently both authors are ignoring ME instead of unknown keywords... Maybe I can work on a patch for CVSup to add support for commitid instead, but I fear no one takes care of it. Thank you for your time and attention.