From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Broken bootstrap in r113623 Date: Wed, 31 Jul 2013 19:28:26 +0300 Message-ID: <83iozqwv6d.fsf@gnu.org> References: <51F92317.5090103@yandex.ru> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1375289162 17793 80.91.229.3 (31 Jul 2013 16:46:02 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 31 Jul 2013 16:46:02 +0000 (UTC) Cc: xfq.free@gmail.com, emacs-devel@gnu.org To: Dmitry Antipov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jul 31 18:46:04 2013 Return-path: Envelope-to: ged-emacs-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 1V4ZXI-000229-Ih for ged-emacs-devel@m.gmane.org; Wed, 31 Jul 2013 18:46:04 +0200 Original-Received: from localhost ([::1]:32770 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V4ZXH-0003bn-Vi for ged-emacs-devel@m.gmane.org; Wed, 31 Jul 2013 12:46:03 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:54465) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V4ZX8-0003bY-Uo for emacs-devel@gnu.org; Wed, 31 Jul 2013 12:46:01 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1V4ZX3-0008AR-F1 for emacs-devel@gnu.org; Wed, 31 Jul 2013 12:45:54 -0400 Original-Received: from mtaout23.012.net.il ([80.179.55.175]:44960) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V4ZG7-0005gz-1N for emacs-devel@gnu.org; Wed, 31 Jul 2013 12:28:19 -0400 Original-Received: from conversion-daemon.a-mtaout23.012.net.il by a-mtaout23.012.net.il (HyperSendmail v2007.08) id <0MQT003006ZG7000@a-mtaout23.012.net.il> for emacs-devel@gnu.org; Wed, 31 Jul 2013 19:28:17 +0300 (IDT) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout23.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0MQT003AB7321SA0@a-mtaout23.012.net.il>; Wed, 31 Jul 2013 19:28:14 +0300 (IDT) In-reply-to: <51F92317.5090103@yandex.ru> X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: Solaris 10 X-Received-From: 80.179.55.175 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:162299 Archived-At: > Date: Wed, 31 Jul 2013 18:45:43 +0400 > From: Dmitry Antipov > Cc: Xue Fuqiao > > ... > make[3]: Entering directory `/home/dima/work/stuff/emacs/trunk/build-debug/doc/emacs' > /bin/makeinfo --force --enable-encoding -I /home/dima/work/stuff/emacs/trunk/doc/emacs --no-split -o /home/dima/work/stuff/emacs/trunk/doc/emacs/../../info/emacs.info > /home/dima/work/stuff/emacs/trunk/doc/emacs/emacs.texi > /home/dima/work/stuff/emacs/trunk/doc/emacs/emacs.texi:547: Cross reference to nonexistent node `Disabling Multibyte' (perhaps incorrect sectioning?). > make[3]: *** [/home/dima/work/stuff/emacs/trunk/doc/emacs/../../info/emacs.info] Error 1 > ... Fixed. Xue, please in the future always run "make info" whenever you make any changes in the manual. Otherwise, the risk of gratuitously breaking the build is quite high. Please also make a point of mentioning _all_ of your changes in ChangeLog entries (in this case, the removal of the "Disabling Multibyte" node was never mentioned). Finally, please use meaningful commit messages. Something like "Doc fix" does not have any meaningful information, and thus is useless. We use "Doc fix" when making changes to doc strings of Lisp functions, but then we always state the name of the function whose doc string was fixed, and in any case calling 5 non-trivial changes "Doc fix" is not a good idea. Think about the plight of someone who wants to get a quick overview of a series of changes by doing "bzr log -l10 --line".