Date: Tue, 27 Nov 2007 18:25:51 -0600 (CST) From: Wes Morgan <morganw@chemikals.org> To: "Aryeh M. Friedman" <aryeh.friedman@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: bypassing certain cvs commits Message-ID: <alpine.BSF.0.99999.0711271819360.2001@ibyngvyr.purzvxnyf.bet> In-Reply-To: <474C28C1.4000204@gmail.com> References: <474C28C1.4000204@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.0.99999.0711271819360.2001>