On 8 October 2011 03:25, Jeremy Chadwick free...@jdc.parodius.com wrote:
On Fri, Oct 07, 2011 at 02:36:25PM -0400, Aryeh Friedman wrote:
Just a quick note the repo was synced about 15 mins before this
On Fri, Oct 7, 2011 at 2:34 PM, Aryeh Friedman
aryeh.fried...@gmail.comwrote:
I have a
The orginal issue resolved it self over night... but note that I waited 2
days for cvsup10.us.freebsd.org to sync in case everything everyone raised
in this thread where the cause
On Sat, Oct 8, 2011 at 5:29 AM, Chris Rees cr...@freebsd.org wrote:
On 8 October 2011 03:25, Jeremy Chadwick
On Sat, Oct 08, 2011 at 10:29:19AM +0100, Chris Rees wrote:
On 8 October 2011 03:25, Jeremy Chadwick free...@jdc.parodius.com wrote:
On Fri, Oct 07, 2011 at 02:36:25PM -0400, Aryeh Friedman wrote:
Just a quick note the repo was synced about 15 mins before this
On Fri, Oct 7, 2011 at 2:34
On Sat, Oct 08, 2011 at 05:38:31AM -0400, Aryeh Friedman wrote:
The orginal issue resolved it self over night... but note that I waited 2
days for cvsup10.us.freebsd.org to sync in case everything everyone raised
in this thread where the cause
On Sat, Oct 8, 2011 at 5:29 AM, Chris Rees
On Sat, Oct 8, 2011 at 5:45 AM, Jeremy Chadwick free...@jdc.parodius.comwrote:
On Sat, Oct 08, 2011 at 05:38:31AM -0400, Aryeh Friedman wrote:
The orginal issue resolved it self over night... but note that I waited 2
days for cvsup10.us.freebsd.org to sync in case everything everyone
raised
On 08/10/2011 10:43, Jeremy Chadwick wrote:
175 STARTTIME!= LC_ALL=C date
176 CHECK_TIME!= find ${.CURDIR}/sys/sys/param.h -mtime -0s
177 .if !empty(CHECK_TIME)
178 .error check your date/time: ${STARTTIME}
179 .endif
180
The OP is using HEAD (or maybe RELENG_9? [1]), but I would hope the
On Thu, Oct 6, 2011 at 1:32 AM, Li, Qing qing...@bluecoat.com wrote:
[...]
I'm seeing this as well. It's very easy to reproduce:
1. Start listening for routing messages on a non-default FIB, e.g.
setfib 2 route monitor
2. Add any static route within that FIB.
3. The machine I run the test on is
Just on case anyone's not on ports@:
-- Forwarded message --
From: Chris Rees cr...@freebsd.org
Date: 8 Oct 2011 10:30
Subject: Re: [HEADSUP]: ports feature freeze starts soon
To: Thomas Mueller mueller6...@bellsouth.net
Cc: freebsd-po...@freebsd.org, Erwin Lansing
