From owner-svn-src-head@freebsd.org  Fri Oct 19 22:19:52 2018
Return-Path: <owner-svn-src-head@freebsd.org>
Delivered-To: svn-src-head@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 20FACFE8D94;
 Fri, 19 Oct 2018 22:19:52 +0000 (UTC)
 (envelope-from carpeddiem@gmail.com)
Received: from mail-it1-f173.google.com (mail-it1-f173.google.com
 [209.85.166.173])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G3" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id B734970196;
 Fri, 19 Oct 2018 22:19:51 +0000 (UTC)
 (envelope-from carpeddiem@gmail.com)
Received: by mail-it1-f173.google.com with SMTP id c23-v6so5993488itd.5;
 Fri, 19 Oct 2018 15:19:51 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:mime-version:references:in-reply-to:from:date
 :message-id:subject:to:cc;
 bh=AMPuOebLF4A10e0h+wTjQgUU3/bEW8hMA7psOA+lEqI=;
 b=Kqkrof7iF+CQi2Ba7kcHANiMCycwViDs1F4yY/NjDuK8BEuYDKajjHEKkYp8k1LDb5
 2bqHvUvBnwP1ZF8pM0zb/ug463CyWr4JZ0h6GLy6ce1y0xnQnQaBQSbpLxMb9ZAkN/yd
 J2XXoiej0M7ASgrPBStWHF1Sq1GvPyYmjG2BFXJqY6x1QIlJbh5pJjibq205T+POUtKw
 osSNv/4S60+Q7ec0EH1bhY2QERBu/wxgVc85BPK1oc5PMdbYF+ALE1/W9EwvH54x+Qgx
 zwnMl3KapsSqgBtsUAV6noUBzTHTvAOwzb604816lxGtkgVXh5kMXvtCa9wsunV4CZt3
 YNhA==
X-Gm-Message-State: ABuFfojxgf084o3YskLkUkGSksGiDO8vgeDVGTu1I1lgLe6uDlOHwZ+3
 CUGi683DVwr47ODlt1NgClgTi5GCdgw3C7QDbPpdPaMN
X-Google-Smtp-Source: ACcGV62WWjMlG9ZnlS6QnDn782lLdFSOe42UA/TuqYSoVRbkZytUQHc+TCT56QDRC/DH62bzp2VsiX3ZZZxCl1WUH1w=
X-Received: by 2002:a24:430d:: with SMTP id
 s13-v6mr4308664itb.33.1539987590727; 
 Fri, 19 Oct 2018 15:19:50 -0700 (PDT)
MIME-Version: 1.0
References: <201810132126.w9DLQ73C022496@repo.freebsd.org>
 <CAALwa8k5k7T2Xy6jSq0bbj+iq0T_FwctOZ-=ZLkCU6eS1+CoKg@mail.gmail.com>
 <CAPyFy2Cv2ydYWmBvWxoM9ACw2iCnq7xfsngEyOPF7XNK7P8ckA@mail.gmail.com>
 <CAPyFy2B-Oc8rVk_iBd8z6ecK_htEF41CCEZ_9=29zMGwap5aKg@mail.gmail.com>
 <CAALwa8=rUZh=VaQL0Ln6TsrfaK7maAhdG88AD1ZyDc-UpDMxSQ@mail.gmail.com>
 <CAPyFy2BLHKQ5Tj0LD=4W367t9am0S_XKjEBhPGAz3w8fXbqw3g@mail.gmail.com>
 <alpine.LSU.2.21.1810191551310.3749@anthias.pfeifer.com>
In-Reply-To: <alpine.LSU.2.21.1810191551310.3749@anthias.pfeifer.com>
From: Ed Maste <emaste@freebsd.org>
Date: Fri, 19 Oct 2018 14:21:02 -0400
Message-ID: <CAPyFy2CVv_8KJ4rsgDTXfhrNWYm32CCtG5q+frZBdzO16Rmj+Q@mail.gmail.com>
Subject: Re: svn commit: r339350 - head/contrib/elftoolchain/elfcopy
To: gerald@pfeifer.com
Cc: Antoine Brodin <antoine@freebsd.org>,
 src-committers <src-committers@freebsd.org>, 
 svn-src-all@freebsd.org, svn-src-head@freebsd.org
Content-Type: text/plain; charset="UTF-8"
X-BeenThere: svn-src-head@freebsd.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: SVN commit messages for the src tree for head/-current
 <svn-src-head.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/svn-src-head>,
 <mailto:svn-src-head-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/svn-src-head/>
List-Post: <mailto:svn-src-head@freebsd.org>
List-Help: <mailto:svn-src-head-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/svn-src-head>,
 <mailto:svn-src-head-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Oct 2018 22:19:52 -0000

On Fri, 19 Oct 2018 at 09:54, Gerald Pfeifer <gerald@pfeifer.com> wrote:
>
> On Thu, 18 Oct 2018, Ed Maste wrote:
> > I think this is probably the right approach, although I also have an
> > ELF Tool Chain fix in D17596 which is waiting on the code freeze to
> > end.
>
> I'm a little confused:  This was broken most recently (as the mail
> bomb that my inbox received from the pkg cluster and others indicates),
> so at this point in the release cycle shouldn't
>  (a) the change causing all this be reverted, *or*

Unfortunately there are subsequent changes that depend on the original
fix which would also have to be unwound, it's not as easy as just
reverting this one.

>  (b) a follow-up patch committed immediately,
> whatever looks less risky?

The follow-up patch is ready but is waiting on re@. At this point I
expect I can commit in two days and then will need to re-request to
merge to stable/12.