From owner-freebsd-testing@freebsd.org Sun Jul 12 02:29:41 2015 Return-Path: Delivered-To: freebsd-testing@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CC6829E7B for ; Sun, 12 Jul 2015 02:29:41 +0000 (UTC) (envelope-from crodr001@gmail.com) Received: from mail-yk0-x230.google.com (mail-yk0-x230.google.com [IPv6:2607:f8b0:4002:c07::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9335CFA1 for ; Sun, 12 Jul 2015 02:29:41 +0000 (UTC) (envelope-from crodr001@gmail.com) Received: by ykay190 with SMTP id y190so15152608yka.3 for ; Sat, 11 Jul 2015 19:29:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=3SJVRRBg8HfPx2lO8ETEFLXwXV1pljrwiKm+N3U/Xnw=; b=RdQzN0h+z6AlWfs/cNX9OPKIegj7HS/8WDqqcVZF6WRjgr58BQp83LjWKzZJEqetoT TlcLoBL0KFBD/vfNCfUirMSk7IVkH28G3p78dEmj0+pQpeENRim52JEYlLoPzQABEgdb k1o0LOq+fHvEyTyOyaBDm2yVtOjCfnz4MnDAdpcGhYp1hFxwT2chJ1Nc6Epnn8LoflO2 EH4xRBoPTPIdlfvGf4iJW5EmaRtimYiC3WL48gE01q3H1uNg7n74HeZR0CZYlB2kIj1c Uwrek1/wuLcjNyaLJjFYalWwM6/D6XlXvYQvHKzZ2/ha7rchjj+XXtQqm21bL98UHw/T WbvQ== MIME-Version: 1.0 X-Received: by 10.170.110.82 with SMTP id c79mr31308116ykb.113.1436668178936; Sat, 11 Jul 2015 19:29:38 -0700 (PDT) Sender: crodr001@gmail.com Received: by 10.37.11.70 with HTTP; Sat, 11 Jul 2015 19:29:38 -0700 (PDT) In-Reply-To: References: Date: Sat, 11 Jul 2015 22:29:38 -0400 X-Google-Sender-Auth: K4iM7ufmB3LpPNg-FEaoctxgXMU Message-ID: Subject: Re: Need help reducing gcc compiler warnings in BSD From: Craig Rodrigues To: "users@dragonflybsd.org" Cc: "freebsd-testing@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-testing@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Testing on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Jul 2015 02:29:41 -0000 Hi, Yes, I agree that formal collaboration is overkill for this stuff, but I thought I would inform the DragonFlyBSD community, because I have been benefiting by taking good fixes done to the DragonFlyBSD tree. One advantage of the Jenkins build is that it enumerates the compiler warnings in a table, so it is easy to track over time if compiler warnings increase or decrease as code changes are made, so DragonFlyBSD users can monitor that if they wish. One item I could use help with is that gcc 4.9 compiles FreeBSD's i386/boot2 to greater than 8192 bytes, so it is unusable: https://lists.freebsd.org/pipermail/freebsd-testing/2015-March/000887.html I see that DragonFlyBSD has changed a lot of the boot code compared to FreeBSD. I'm not familiar with all the changes. Are there fixes done in this area for DragonFlyBSD that could be pushed back to FreeBSD? -- Craig On Fri, Jul 10, 2015 at 3:56 PM, Matthew Dillon wrote: > I'm not sure the work load is high enough to require a formal > collaboration. We just fix things as they come up for the most part. > Sascha has been doing WARNS related cleanups on the codebase and slowly > bumping up the WARNS level for various parts of the build for years, which > reduces problems going forwards. It's mostly a matter of being proactive > about it. > > -Matt > > > On Fri, Jul 10, 2015 at 7:52 AM, Craig Rodrigues > wrote: > >> Hi, >> >> I set up this Jenkins job which builds FreeBSD with gcc 4.9, and reports >> all the compiler warnings here: >> >> >> https://jenkins.freebsd.org/job/FreeBSD_HEAD_amd64_gcc4.9/177/warnings17Result/ >> >> I have been working with other people like Marcelo Araujo to >> reduce the gcc compiler warnings on FreeBSD, even though >> the default system compiler for FreeBSD is clang. >> I have noticed that a lot of fixes to the problems have been down >> in DragonFlyBSD. I have imported some of these fixes, especially ones >> done by >> Sascha Wildner, such as this one: >> >> https://lists.freebsd.org/pipermail/svn-src-head/2015-May/072562.html >> >> Is there a way that we can collaborate across the FreeBSD and DragonFlyBSD >> projects to reduce gcc compiler warnings? That it would be quite nice. >> It would make code easier to share, and improve the code overall. >> >> Thanks. >> -- >> Craig >> >> > From owner-freebsd-testing@freebsd.org Sun Jul 12 06:44:33 2015 Return-Path: Delivered-To: freebsd-testing@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A286F999768 for ; Sun, 12 Jul 2015 06:44:33 +0000 (UTC) (envelope-from mattdillonbsd@gmail.com) Received: from mail-yk0-x22c.google.com (mail-yk0-x22c.google.com [IPv6:2607:f8b0:4002:c07::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 69E0A1FAE; Sun, 12 Jul 2015 06:44:33 +0000 (UTC) (envelope-from mattdillonbsd@gmail.com) Received: by ykee186 with SMTP id e186so92995065yke.2; Sat, 11 Jul 2015 23:44:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=UyFjGT24rXnVwB8+2suYb6FY1HRXVbaLe4o1QKa4QeM=; b=pQ5QNZSk8vBgHmYTzqS2WyU0V9+GdVgMklDoJmi586uvY+ma/iLaywq87l6C/qQm7i RKf/E5nHgMZoR+jXFkcDAlIOTLbODh538pBN5oCHR96tV89vskHQ0XxBXum5QqkGtDru ofJ5/+7/svz23XRtswPTZGp594bYMI9Lgj+SK28tt5gNmn9lrWyGO7C62qR3SKYMmNpT cTCSJesxxJ9soT4afVrYtFvKXhY6UGPCoUPqaAab2XOXhv6TIhLb/IMZgpdhADZXFgkL FqYpFC12Pgja5tY3O2lEh2VNRGWbNjuakHiTWmPZ/SDRZ1HjNAT6au0r6QzBzYpGzzXS FatA== MIME-Version: 1.0 X-Received: by 10.129.84.4 with SMTP id i4mr32332233ywb.77.1436683472384; Sat, 11 Jul 2015 23:44:32 -0700 (PDT) Sender: mattdillonbsd@gmail.com Received: by 10.129.52.75 with HTTP; Sat, 11 Jul 2015 23:44:32 -0700 (PDT) In-Reply-To: References: Date: Sat, 11 Jul 2015 23:44:32 -0700 X-Google-Sender-Auth: aB190RhRME8yTG4Ub0liIr57I1k Message-ID: Subject: Re: Need help reducing gcc compiler warnings in BSD From: Matthew Dillon To: Craig Rodrigues Cc: "users@dragonflybsd.org" , "freebsd-testing@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-testing@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Testing on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Jul 2015 06:44:33 -0000 Well, the boot code is a bit of a crap-shoot, because a lot of it is related to working around bugs in various BIOSes rather than actual bug fixes in the boot code itself. Changes can sometimes break one platform while fixing another. So wholesale copying of boot work in either direction without a huge amount of testing will meet with a great deal of resistance. -Matt On Sat, Jul 11, 2015 at 7:29 PM, Craig Rodrigues wrote: > Hi, > > Yes, I agree that formal collaboration is overkill for this stuff, but I > thought I would inform > the DragonFlyBSD community, because I have been benefiting by taking good > fixes > done to the DragonFlyBSD tree. One advantage of the Jenkins build is that > it enumerates > the compiler warnings in a table, so it is easy to track over time if > compiler warnings increase or decrease > as code changes are made, so DragonFlyBSD users can monitor that if they > wish. > > One item I could use help with is that gcc 4.9 compiles FreeBSD's > i386/boot2 to > greater than 8192 bytes, so it is unusable: > https://lists.freebsd.org/pipermail/freebsd-testing/2015-March/000887.html > > I see that DragonFlyBSD has changed a lot of the boot code compared to > FreeBSD. > I'm not familiar with all the changes. Are there fixes done in this area > for DragonFlyBSD > that could be pushed back to FreeBSD? > > -- > Craig > > On Fri, Jul 10, 2015 at 3:56 PM, Matthew Dillon > wrote: > >> I'm not sure the work load is high enough to require a formal >> collaboration. We just fix things as they come up for the most part. >> Sascha has been doing WARNS related cleanups on the codebase and slowly >> bumping up the WARNS level for various parts of the build for years, which >> reduces problems going forwards. It's mostly a matter of being proactive >> about it. >> >> -Matt >> >> >> On Fri, Jul 10, 2015 at 7:52 AM, Craig Rodrigues >> wrote: >> >>> Hi, >>> >>> I set up this Jenkins job which builds FreeBSD with gcc 4.9, and reports >>> all the compiler warnings here: >>> >>> >>> https://jenkins.freebsd.org/job/FreeBSD_HEAD_amd64_gcc4.9/177/warnings17Result/ >>> >>> I have been working with other people like Marcelo Araujo to >>> reduce the gcc compiler warnings on FreeBSD, even though >>> the default system compiler for FreeBSD is clang. >>> I have noticed that a lot of fixes to the problems have been down >>> in DragonFlyBSD. I have imported some of these fixes, especially ones >>> done by >>> Sascha Wildner, such as this one: >>> >>> https://lists.freebsd.org/pipermail/svn-src-head/2015-May/072562.html >>> >>> Is there a way that we can collaborate across the FreeBSD and >>> DragonFlyBSD >>> projects to reduce gcc compiler warnings? That it would be quite nice. >>> It would make code easier to share, and improve the code overall. >>> >>> Thanks. >>> -- >>> Craig >>> >>> >> > From owner-freebsd-testing@freebsd.org Sun Jul 12 06:50:10 2015 Return-Path: Delivered-To: freebsd-testing@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B7CE4999829 for ; Sun, 12 Jul 2015 06:50:10 +0000 (UTC) (envelope-from mattdillonbsd@gmail.com) Received: from mail-yk0-x22c.google.com (mail-yk0-x22c.google.com [IPv6:2607:f8b0:4002:c07::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 74F0C1BA; Sun, 12 Jul 2015 06:50:10 +0000 (UTC) (envelope-from mattdillonbsd@gmail.com) Received: by ykax123 with SMTP id x123so45663060yka.1; Sat, 11 Jul 2015 23:50:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=nEEqNZj2ijddMjsZywuy6qxmemEbmf7eGTPMhnuQUVU=; b=M0vzyPIAQ7QnfvCXw+T9qAbxmxbj0kBU+n/wAPxWbiaCvZ/41hMxrSNGVRFpNZpIS8 FHSfe6UHTzcRKSh+c81NWnGYZ10fvCm8wyvLKvQRvg/4Mx5DgP4F/bbmhQfdkl/Dx+b9 2GyQid6KaQ4apXD4xkZYf/31Y/ikkcqAKGunjVHqvQzqGwurBkSh2H/V300WCiRE7OD1 Ys6JEoEpaOFp86sZsKM11shcLmCvN2iCkditp0OvYTV0zAJFMRVb62XNnlwNqPVegI1x JcHTJGm6x5JjwrTPO98b3sC2kPI+GmxtXMpi74eHnV8fpnrtfuQ6Xter7jUf1izqrBgJ ncfg== MIME-Version: 1.0 X-Received: by 10.129.4.20 with SMTP id 20mr15093535ywe.36.1436683809731; Sat, 11 Jul 2015 23:50:09 -0700 (PDT) Sender: mattdillonbsd@gmail.com Received: by 10.129.52.75 with HTTP; Sat, 11 Jul 2015 23:50:09 -0700 (PDT) In-Reply-To: References: Date: Sat, 11 Jul 2015 23:50:09 -0700 X-Google-Sender-Auth: uKT9ltx6-bpjJSMUeyc7ZK7p2_U Message-ID: Subject: Re: Need help reducing gcc compiler warnings in BSD From: Matthew Dillon To: Craig Rodrigues Cc: "users@dragonflybsd.org" , "freebsd-testing@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-testing@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Testing on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Jul 2015 06:50:10 -0000 On gcc-4.9 and other gcc related bloat in the boot code, you need to experiment with the optimization options. Some optimizations can make code smaller, some can make it bigger. Sometimes by a lot. We've hit the boot2 limit ourselves a few times though not in a long while so I don't remember the precise changes that were made. One thing that can be helpful is to use objdump -d on boot2.out (somewhere in /usr/obj when you build the boot code), comparing the output before and after to track down where the size changes are centered. boot2 is relatively small code so a side-by-side comparison in two xterms is doable. diff won't work well in this case. -Matt On Sat, Jul 11, 2015 at 11:44 PM, Matthew Dillon wrote: > Well, the boot code is a bit of a crap-shoot, because a lot of it is > related to working around bugs in various BIOSes rather than actual bug > fixes in the boot code itself. Changes can sometimes break one platform > while fixing another. So wholesale copying of boot work in either > direction without a huge amount of testing will meet with a great deal of > resistance. > > -Matt > > On Sat, Jul 11, 2015 at 7:29 PM, Craig Rodrigues > wrote: > >> Hi, >> >> Yes, I agree that formal collaboration is overkill for this stuff, but I >> thought I would inform >> the DragonFlyBSD community, because I have been benefiting by taking good >> fixes >> done to the DragonFlyBSD tree. One advantage of the Jenkins build is >> that it enumerates >> the compiler warnings in a table, so it is easy to track over time if >> compiler warnings increase or decrease >> as code changes are made, so DragonFlyBSD users can monitor that if they >> wish. >> >> One item I could use help with is that gcc 4.9 compiles FreeBSD's >> i386/boot2 to >> greater than 8192 bytes, so it is unusable: >> https://lists.freebsd.org/pipermail/freebsd-testing/2015-March/000887.html >> >> I see that DragonFlyBSD has changed a lot of the boot code compared to >> FreeBSD. >> I'm not familiar with all the changes. Are there fixes done in this area >> for DragonFlyBSD >> that could be pushed back to FreeBSD? >> >> -- >> Craig >> >> On Fri, Jul 10, 2015 at 3:56 PM, Matthew Dillon >> wrote: >> >>> I'm not sure the work load is high enough to require a formal >>> collaboration. We just fix things as they come up for the most part. >>> Sascha has been doing WARNS related cleanups on the codebase and slowly >>> bumping up the WARNS level for various parts of the build for years, which >>> reduces problems going forwards. It's mostly a matter of being proactive >>> about it. >>> >>> -Matt >>> >>> >>> On Fri, Jul 10, 2015 at 7:52 AM, Craig Rodrigues >>> wrote: >>> >>>> Hi, >>>> >>>> I set up this Jenkins job which builds FreeBSD with gcc 4.9, and reports >>>> all the compiler warnings here: >>>> >>>> >>>> https://jenkins.freebsd.org/job/FreeBSD_HEAD_amd64_gcc4.9/177/warnings17Result/ >>>> >>>> I have been working with other people like Marcelo Araujo to >>>> reduce the gcc compiler warnings on FreeBSD, even though >>>> the default system compiler for FreeBSD is clang. >>>> I have noticed that a lot of fixes to the problems have been down >>>> in DragonFlyBSD. I have imported some of these fixes, especially ones >>>> done by >>>> Sascha Wildner, such as this one: >>>> >>>> https://lists.freebsd.org/pipermail/svn-src-head/2015-May/072562.html >>>> >>>> Is there a way that we can collaborate across the FreeBSD and >>>> DragonFlyBSD >>>> projects to reduce gcc compiler warnings? That it would be quite nice. >>>> It would make code easier to share, and improve the code overall. >>>> >>>> Thanks. >>>> -- >>>> Craig >>>> >>>> >>> >> > From owner-freebsd-testing@freebsd.org Tue Jul 14 15:25:29 2015 Return-Path: Delivered-To: freebsd-testing@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1CABC9A1D33 for ; Tue, 14 Jul 2015 15:25:29 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 09157AFB for ; Tue, 14 Jul 2015 15:25:29 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t6EFPSLf064790 for ; Tue, 14 Jul 2015 15:25:28 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-testing@freebsd.org Subject: [Bug 201285] tools/regression/lib/libc/nss/test-getaddr.c:450: possible missing break ? Date: Tue, 14 Jul 2015 15:25:29 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: tests X-Bugzilla-Version: 10.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-testing@freebsd.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-testing@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Testing on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Jul 2015 15:25:29 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201285 --- Comment #1 from commit-hook@freebsd.org --- A commit references this bug: Author: brueffer Date: Tue Jul 14 15:24:51 UTC 2015 New revision: 285543 URL: https://svnweb.freebsd.org/changeset/base/285543 Log: Add a missing break statement, which made the code default to IPv6. PR: 201285 Submitted by: David Binderman MFC after: 1 week Changes: head/tools/regression/lib/libc/nss/test-getaddr.c -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-testing@freebsd.org Tue Jul 14 15:33:50 2015 Return-Path: Delivered-To: freebsd-testing@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E40669A1EC7 for ; Tue, 14 Jul 2015 15:33:50 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CFF11C1 for ; Tue, 14 Jul 2015 15:33:50 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t6EFXomN073469 for ; Tue, 14 Jul 2015 15:33:50 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-testing@freebsd.org Subject: [Bug 201285] tools/regression/lib/libc/nss/test-getaddr.c:450: possible missing break ? Date: Tue, 14 Jul 2015 15:33:50 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: tests X-Bugzilla-Version: 10.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: brueffer@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: brueffer@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to bug_status cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-testing@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Testing on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Jul 2015 15:33:51 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201285 Christian Brueffer changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-testing@freebsd.org |brueffer@FreeBSD.org Status|New |In Progress CC| |brueffer@FreeBSD.org --- Comment #2 from Christian Brueffer --- Fixed in HEAD, MFC pending. Thanks (and sorry for misspelling your name in the previous commits)! -- You are receiving this mail because: You are the assignee for the bug.