[Bismark-devel] Bismark-devel post from feamster at cc.gatech.edu requires approval

[Brian Poole]

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,
<bismark-devel-owner at lists.bufferbloat.net>wrote:

> As list administrator, your authorization is requested for the
> following mailing list posting:
>
>    List:    Bismark-devel at lists.bufferbloat.net
>    From:    feamster at 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 <feamster at cc.gatech.edu>
> To: bismark-devel at 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 at 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.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.bufferbloat.net/pipermail/bismark-devel/attachments/20110408/1941d1df/attachment-0002.html>