From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 58258 invoked by alias); 27 Oct 2016 12:56:25 -0000 Mailing-List: contact libffi-discuss-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libffi-discuss-owner@sourceware.org Received: (qmail 58177 invoked by uid 89); 27 Oct 2016 12:56:24 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW autolearn=unavailable version=3.3.2 spammy= X-HELO: einhorn.in-berlin.de Received: from einhorn.in-berlin.de (HELO einhorn.in-berlin.de) (192.109.42.8) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 27 Oct 2016 12:56:20 +0000 X-Envelope-From: doko@ubuntu.com Received: from [192.168.178.26] (ip5f5af460.dynamic.kabel-deutschland.de [95.90.244.96]) (authenticated bits=0) by einhorn.in-berlin.de (8.14.4/8.14.4/Debian-8+deb8u1) with ESMTP id u9RCts14018858 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 27 Oct 2016 14:55:54 +0200 To: gcc Development Cc: "libffi-discuss@sourceware.org" , Ian Lance Taylor From: Matthias Klose Subject: libffi maintenance within GCC? Message-ID: <48a433ca-9f6d-3b5b-9485-64261d812b66@ubuntu.com> Date: Thu, 27 Oct 2016 12:56:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-IsSubscribed: yes X-SW-Source: 2016/txt/msg00048.txt.bz2 With the removal of libgcj, the only user of libffi in GCC is libgo, however there is now no maintainer listed anymore for libffi in the MAINTAINERS file, and the libffi subdir is a bit outdated compared to the libffi upstream repository (got aware of this by libffi issue #197). Who would be responsible now to update / review libffi patches, just the global reviewers, or should libffi be maintained by the libgo maintainers? Matthias