From owner-freebsd-current@FreeBSD.ORG Wed Nov 28 00:56:27 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7051E16A417 for ; Wed, 28 Nov 2007 00:56:27 +0000 (UTC) (envelope-from morganw@chemikals.org) Received: from tiamat.relinetworks.com (tiamat.relinetworks.com [204.214.92.162]) by mx1.freebsd.org (Postfix) with ESMTP id 3558F13C465 for ; Wed, 28 Nov 2007 00:56:27 +0000 (UTC) (envelope-from morganw@chemikals.org) Received: from volatile.chemikals.org (root@r74-193-170-223.bssrcmta01.bscyla.by.dh.suddenlink.net [74.193.170.223] (may be forged)) by tiamat.relinetworks.com (8.14.1/8.14.1) with ESMTP id lAS0PrJ6020896; Tue, 27 Nov 2007 19:25:53 -0500 (EST) (envelope-from morganw@chemikals.org) Received: from localhost (morganw@localhost [127.0.0.1]) by volatile.chemikals.org (8.14.2/8.14.2) with ESMTP id lAS0Pp4I004511; Tue, 27 Nov 2007 18:25:52 -0600 (CST) (envelope-from morganw@chemikals.org) Date: Tue, 27 Nov 2007 18:25:51 -0600 (CST) From: Wes Morgan To: "Aryeh M. Friedman" In-Reply-To: <474C28C1.4000204@gmail.com> Message-ID: References: <474C28C1.4000204@gmail.com> User-Agent: Alpine 0.99999 (BSF 796 2007-11-08) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: bypassing certain cvs commits 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: Wed, 28 Nov 2007 00:56:27 -0000 On Tue, 27 Nov 2007, Aryeh M. Friedman wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > As per my detailed comments to Jason > http://lists.freebsd.org/pipermail/cvs-src/2007-November/084307.html > is broken but I want to update everything else how do I by pass the > ref'ed commit? You do realize that running -current, especially so soon after a branch, is virtually expected to have this kind of breakage from time to time, sometimes frequently. The best and most productive course of action would probably be to contact the committer directly rather than creating a lot of unneeded chatter on multiple mailing lists. Unless there is some critical "must-have" feature in -current that isn't available in the 7-stable tree, perhaps you'd be better off tracking that instead. 7.0 is going to be fantastic, and I have not yet seen anything committed to -current that would make me want to track it instead of 7, and I've tracked -current since 4-current. WNM