From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-14-ewr.dyndns.com (mxout-082-ewr.mailhop.org [216.146.33.82]) by lists.bufferbloat.net (Postfix) with ESMTP id 14F162E034E for ; Fri, 8 Apr 2011 20:01:42 -0700 (PDT) Received: from scan-11-ewr.mailhop.org (scan-11-ewr.local [10.0.141.229]) by mail-14-ewr.dyndns.com (Postfix) with ESMTP id 80B4F9CBDB7 for ; Sat, 9 Apr 2011 03:01:41 +0000 (UTC) X-Spam-Score: 0.0 () X-Mail-Handler: MailHop by DynDNS X-Originating-IP: 209.85.220.171 Received: from mail-vx0-f171.google.com (mail-vx0-f171.google.com [209.85.220.171]) by mail-14-ewr.dyndns.com (Postfix) with ESMTP id 3BC449CB349 for ; Sat, 9 Apr 2011 03:01:41 +0000 (UTC) Received: by vxc40 with SMTP id 40so4996776vxc.16 for ; Fri, 08 Apr 2011 20:01:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=AD9nLMX0nEPJ5LnaxEyXuIelwhEozJXhgDD9Fkrqnek=; b=BMj4R2D7desKtyFURlng3mzam+4MHAcWEtGTRFeBbnhqZ9/tJIQguWMzP/Fw5fxDXt qyV5QhKHl9YnpqD4JRPhTVbUCnKEG8o//RF4hv9weYK5WKbQVDwPVmYm1msJsPdlS5L8 FAuUUFrHSCUSVtv70Zd73QJelQ05eeGKJo/z4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=p4RD4HYgNMR2x1MG5hz7D8yVmQYoQD3I+z3sFvO/H8gGUHRs2Zb6diWxDummaiuUW7 zr5ICK55xwRsm8/Fr9jIOA99CNZqE89HGjmBsPmaDt4y6V0yVVcpgy6aep3JbPr70SHo YY0YJofjG0uNCM16XHNZhBrNFzqw7eBcRrE6Q= MIME-Version: 1.0 Received: by 10.52.173.176 with SMTP id bl16mr1598599vdc.41.1302318100981; Fri, 08 Apr 2011 20:01:40 -0700 (PDT) Received: by 10.220.180.196 with HTTP; Fri, 8 Apr 2011 20:01:40 -0700 (PDT) In-Reply-To: References: Date: Fri, 8 Apr 2011 23:01:40 -0400 Message-ID: From: Brian Poole To: feamster@cc.gatech.edu, bismark-devel@lists.bufferbloat.net Content-Type: multipart/alternative; boundary=bcaec51ba477cb298304a0738f1c X-Mailman-Approved-At: Sun, 10 Apr 2011 18:41:50 -0700 Subject: Re: [Bismark-devel] Bismark-devel post from feamster@cc.gatech.edu requires approval X-BeenThere: bismark-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: BISMark related software development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Apr 2011 03:01:43 -0000 --bcaec51ba477cb298304a0738f1c Content-Type: text/plain; charset=ISO-8859-1 It may mean the src tree is offering options that aren't specified in your configuration file. If you load up make menuconfig, exit, and save the results it should add/delete anything that has changed. I wonder if that will fix the warning (or is this a fatal error) ? Two possible options come to mind that might cause this (if its the issue)... New options added since we created the .config or maybe related to feeds (we didn't install some feeds that were there previously..) Brian On Fri, Apr 8, 2011 at 10:24 PM, wrote: > As list administrator, your authorization is requested for the > following mailing list posting: > > List: Bismark-devel@lists.bufferbloat.net > From: feamster@cc.gatech.edu > Subject: warning during build > Reason: Post to moderated list > > At your convenience, visit: > > https://lists.bufferbloat.net/admindb/bismark-devel > > to approve or deny the request. > > > ---------- Forwarded message ---------- > From: Nick Feamster > To: bismark-devel@lists.bufferbloat.net > Date: Fri, 8 Apr 2011 22:24:22 -0400 > Subject: warning during build > "WARNING: your configuration is out of sync. Please run make menuconfig, > oldconfig or defconfig!" > > I did follow our build instructions... I wonder if I did something our of > order. > > -Nick > > ---------- Forwarded message ---------- > From: bismark-devel-request@lists.bufferbloat.net > To: > Date: Fri, 08 Apr 2011 19:24:34 -0700 > Subject: confirm d02d4fb4aafabb63c173c1f5b960d08de9c729a4 > If you reply to this message, keeping the Subject: header intact, > Mailman will discard the held message. Do this if the message is > spam. If you reply to this message and include an Approved: header > with the list password in it, the message will be approved for posting > to the list. The Approved: header can also appear in the first line > of the body of the reply. > --bcaec51ba477cb298304a0738f1c Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable It may mean the src tree is offering options that aren't specified in y= our configuration file.

If you load up make menuconfig, exit, and sa= ve the results it should add/delete anything that has changed. I wonder if = that will fix the warning (or is this a fatal error) ?

Two possible options come to mind that might cause this (if its the iss= ue)... New options added since we created the .config or maybe related to f= eeds (we didn't install some feeds that were there previously..)

Brian

On Fri, Apr 8, 2011 at 10:24 PM= , <bismark-devel-owner@lists.bufferbloat.net&= gt; wrote:
As list administrator, your authorizati= on is requested for the
following mailing list posting:

=A0 =A0List: =A0 =A0Bismark-devel@lists.bufferbloat.net
=A0 =A0From: =A0 =A0feamster@cc.gatech.edu
=A0 =A0Subject: warning during build
=A0 =A0Reason: =A0Post to moderated list

At your convenience, visit:

=A0 =A0https://lists.bufferbloat.net/admindb/bismark-devel

to approve or deny the request.


---------- Forwarded message ----------
From:=A0Nick= Feamster <f= eamster@cc.gatech.edu>
To:=A0bismark-devel@lists.bufferbloat.net
Date:=A0Fri, 8 Apr 2011 22:24:22 -0400
Subject:=A0warning during build"WARNING: your configuration is out of sync. Please run make menucon= fig, oldconfig or defconfig!"

I did follow our build instructions... I wonder if I did something our of o= rder.

-Nick

---------- Forwarded message ----------
From:=A0bisma= rk-devel-request@lists.bufferbloat.net
To:=A0
Date:=A0Fri, 08 Apr= 2011 19:24:34 -0700
Subject:=A0confirm d02d4fb4aafabb63c173c1f5b960d08de9c729a4
If you reply= to this message, keeping the Subject: header intact,
Mailman will discard the held message. =A0Do this if the message is
spam. =A0If you reply to this message and include an Approved: header
with the list password in it, the message will be approved for posting
to the list. =A0The Approved: header can also appear in the first line
of the body of the reply.

--bcaec51ba477cb298304a0738f1c--