From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Andy Wingo Newsgroups: gmane.lisp.guile.devel Subject: Re: Guile's DATAROOTDIR and DATADIR Date: Sat, 16 Jul 2016 11:06:06 +0200 Message-ID: <87oa5yvtoh.fsf@pobox.com> References: <83furb6zs7.fsf@gnu.org> <87shvavmn9.fsf@netris.org> <834m7q7q1x.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1468660009 15610 80.91.229.3 (16 Jul 2016 09:06:49 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 16 Jul 2016 09:06:49 +0000 (UTC) Cc: Mark H Weaver , guile-devel@gnu.org To: Eli Zaretskii Original-X-From: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Sat Jul 16 11:06:41 2016 Return-path: Envelope-to: guile-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1bOLYW-0006WS-9p for guile-devel@m.gmane.org; Sat, 16 Jul 2016 11:06:40 +0200 Original-Received: from localhost ([::1]:36556 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bOLYV-0008Ay-49 for guile-devel@m.gmane.org; Sat, 16 Jul 2016 05:06:39 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:35436) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bOLYE-00089q-Q7 for guile-devel@gnu.org; Sat, 16 Jul 2016 05:06:23 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bOLYC-0007Mj-Qn for guile-devel@gnu.org; Sat, 16 Jul 2016 05:06:21 -0400 Original-Received: from pb-sasl2.pobox.com ([64.147.108.67]:51666 helo=sasl.smtp.pobox.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bOLY7-0007MR-1R; Sat, 16 Jul 2016 05:06:15 -0400 Original-Received: from sasl.smtp.pobox.com (unknown [127.0.0.1]) by pb-sasl2.pobox.com (Postfix) with ESMTP id 9A24B294DA; Sat, 16 Jul 2016 05:06:14 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=from:to:cc :subject:references:date:in-reply-to:message-id:mime-version :content-type; s=sasl; bh=PhVmQkOzvDqxXHzt/F2fCh6CwQM=; b=vJ6xNO Nd0YHykePANDSOuuw0bNsT5RYQQigoLm77Tbn/IFc0W1bBd28qvdbZ7+7FO6RvxU CzLVNbhJzDHcatLDL7G5V4bgKtz2aRXnQuz64HlHCVLJF2FL9P1Dz1uXBIDUMG3p iIqvcCItGUPhn0V10bfAoCAG5RZQZAo2upViY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=from:to:cc :subject:references:date:in-reply-to:message-id:mime-version :content-type; q=dns; s=sasl; b=LqmaRlc3Ua/uoIR6pgz+76etehjrKZ+x 4Q+O+p+Im6PyCf4ceIcbMoTJuM6qADELdF0SKHfd7llGBSW6ycOytJaB8YPnB5+m ojFQJFxMvtZWI5yUeMkhivr4CjSJuEJl2XLvbly5WO9FF9IQukgxLXhY3/PPbo6Q HTLRnNIAX+4= Original-Received: from pb-sasl2.nyi.icgroup.com (unknown [127.0.0.1]) by pb-sasl2.pobox.com (Postfix) with ESMTP id 82E06294D5; Sat, 16 Jul 2016 05:06:14 -0400 (EDT) Original-Received: from clucks (unknown [88.160.190.192]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pb-sasl2.pobox.com (Postfix) with ESMTPSA id 98454294D0; Sat, 16 Jul 2016 05:06:13 -0400 (EDT) In-Reply-To: <834m7q7q1x.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 15 Jul 2016 20:46:02 +0300") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) X-Pobox-Relay-ID: 8BE165FC-4B34-11E6-893F-28A6F1301B6D-02397024!pb-sasl2.pobox.com X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 64.147.108.67 X-BeenThere: guile-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Developers list for Guile, the GNU extensibility library" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Original-Sender: "guile-devel" Xref: news.gmane.org gmane.lisp.guile.devel:18532 Archived-At: On Fri 15 Jul 2016 19:46, Eli Zaretskii writes: > Is it possible to publish the list of ABI incompatibilities between > 2.0.11 and 2.0.12 specifically? Any incompatible change between 2.0.12 and a previous release in the 2.0.x series is a bug. It is impossible to make a list of all bugs in a project of course :) I do not know of any incompatibility introduced in 2.0.12. Andy