From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 129770 invoked by alias); 16 Dec 2019 19:36:11 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 129762 invoked by uid 89); 16 Dec 2019 19:36:11 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham version=3.3.1 spammy=our X-HELO: us-smtp-delivery-1.mimecast.com Received: from us-smtp-2.mimecast.com (HELO us-smtp-delivery-1.mimecast.com) (207.211.31.81) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 16 Dec 2019 19:36:10 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1576524968; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=IbQpBDvNZoAV8xPOzYXmGkv3+/S8xFZNM7/HoHLSiWs=; b=KBFPPtTIrAzVEj4YewrawcMsNx2s/rbFz4NzotmKC4iG3ndFWzGciflJZWxCe47jOiVBCV B7KxkbeQH40TaAl5708cov79JfM8Pd0iiK0yiTIzkEC9+PxVgZRmZA+0P6Ecg2vwwLTxeF 6KQxa8svNVM/cIUrsRGl1PKpV/9y9hs= Received: from mail-wr1-f70.google.com (mail-wr1-f70.google.com [209.85.221.70]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-261-bX92p0PYO1qcq5UnrL1chw-1; Mon, 16 Dec 2019 14:36:07 -0500 Received: by mail-wr1-f70.google.com with SMTP id z15so4247714wrw.0 for ; Mon, 16 Dec 2019 11:36:06 -0800 (PST) Return-Path: Received: from ?IPv6:2001:8a0:f913:f700:56ee:75ff:fe8d:232b? ([2001:8a0:f913:f700:56ee:75ff:fe8d:232b]) by smtp.gmail.com with ESMTPSA id w8sm829862wmd.2.2019.12.16.11.36.04 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 16 Dec 2019 11:36:05 -0800 (PST) Subject: Re: GDB 9.0.90 available for testing To: Eli Zaretskii , Christian Biesinger References: <20191211214745.E1CF0838D4@joel.gnat.com> <83tv604239.fsf@gnu.org> <83o8w83wrc.fsf@gnu.org> Cc: brobecker@adacore.com, gdb-patches@sourceware.org From: Pedro Alves Message-ID: Date: Mon, 16 Dec 2019 19:36:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: <83o8w83wrc.fsf@gnu.org> X-Mimecast-Spam-Score: 0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2019-12/txt/msg00719.txt.bz2 On 12/16/19 7:17 PM, Eli Zaretskii wrote: >> I've had some success in sending a bug report/patch to upstream >> readline. Not sure about ctf. > The questions is whether I fix this in our copy independently of > reporting to upstream, or report upstream, and then someone updates > our copy from upstream. I don't think there's an upstream. I mean, I think libctf is maintained in the binutils-gdb repo. That it's more of a binutils project than a gdb project. See top level MAINTAINERS file: bfd/; binutils/; elfcpp/; gas/; gold/; gprof/; ld/; opcodes/; cpu/; libctf/; BFD's and libctf's parts of include/ binutils: http://sourceware.org/binutils/ Patches to binutils@sourceware.org. Please notify the following of any interface changes: gdb-patches@sourceware.org Thanks, Pedro Alves