The issue I think would be that when the release-trunk buildbots get
upgraded to newer compilers (with more warnings), we would start
getting build-failures that didn't exist when 1.8 etc. were actually
trunk.
Not necessarily a huge issue, assuming the builbots aren't updated all
that frequently.
On Thu, Feb 28, 2013 at 12:37 PM, Jeff Morriss
<jeff.morriss.ws@xxxxxxxxx> wrote:
> morriss@xxxxxxxxxxxxx wrote:
>>
>> http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=47943
>>
>> User: morriss
>> Date: 2013/02/28 08:57 AM
>>
>> Log:
>> Copy over from trunk (in order to solve warnings introduced with r46464
>> and
>> backported to trunk-1.8 with r46672):
>
>
> Is it possible/would it make sense to have the release-trunk buildbots do
> their configure's with "--enable-warnings-as-errors" so we can detect
> warnings being back-ported to those trunks (while not enabling
> warnings-as-errors by default--for users--of course)?
>
> ___________________________________________________________________________
> Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
> Archives: http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
> mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
