From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5512 invoked by alias); 6 Mar 2012 02:40:06 -0000 Received: (qmail 5498 invoked by uid 22791); 6 Mar 2012 02:40:05 -0000 X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from hagrid.ecoscentric.com (HELO mail.ecoscentric.com) (212.13.207.197) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 06 Mar 2012 02:39:42 +0000 Received: by mail.ecoscentric.com (Postfix, from userid 48) id AF6492F78001; Tue, 6 Mar 2012 02:39:41 +0000 (GMT) From: bugzilla-daemon@bugs.ecos.sourceware.org To: unassigned@bugs.ecos.sourceware.org Subject: [Bug 1001501] Fix warnings about type-punned pointers in bsd_tcpip code. X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: eCos X-Bugzilla-Component: TCP/IP X-Bugzilla-Keywords: X-Bugzilla-Severity: minor X-Bugzilla-Who: jifl@ecoscentric.com X-Bugzilla-Status: RESOLVED X-Bugzilla-Priority: low X-Bugzilla-Assigned-To: unassigned@bugs.ecos.sourceware.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Status Resolution In-Reply-To: References: X-Bugzilla-URL: http://bugs.ecos.sourceware.org/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Date: Tue, 06 Mar 2012 02:40:00 -0000 Message-Id: <20120306023937.6DC9E2FB082D@mail.ecoscentric.com> Mailing-List: contact ecos-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: ecos-bugs-owner@sourceware.org X-SW-Source: 2012/txt/msg00448.txt.bz2 Please do not reply to this email. Use the web interface provided at: http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001501 Jonathan Larmour changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |NEXTRELEASE --- Comment #4 from Jonathan Larmour 2012-03-06 02:39:33 GMT --- Marking it as Resolved -> NextRelease is most appropriate, although CurrentRelease is what a lot of people do, so don't worry about exactly which :-). Of course the terminology comes mostly from elsewhere. Strictly CurrentRelease means the fix was made during the alpha or beta stage of the release process - i.e. a release is in the works but not yet final. But there's no big deal about it. Jifl -- Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.