Re: bypassing certain cvs commits
- From: Wes Morgan <morganw@xxxxxxxxxxxxx>
- Date: Tue, 27 Nov 2007 18:25:51 -0600 (CST)
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
_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"
- Follow-Ups:
- Re: bypassing certain cvs commits
- From: Aryeh M. Friedman
- Re: bypassing certain cvs commits
- References:
- bypassing certain cvs commits
- From: Aryeh M. Friedman
- bypassing certain cvs commits
- Prev by Date: Re: 802.11 w/ WEP requires deftxkey explicitly set after 2007-08-24
- Next by Date: Re: 802.11 w/ WEP requires deftxkey explicitly set after 2007-08-24
- Previous by thread: Re: bypassing certain cvs commits
- Next by thread: Re: bypassing certain cvs commits
- Index(es):
Relevant Pages
|
|