From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Stephen J. Turnbull" Newsgroups: gmane.emacs.devel Subject: Re: Merging emacs-23 into trunk Date: Thu, 11 Nov 2010 21:29:17 +0900 Message-ID: <87iq04dowy.fsf@uwakimon.sk.tsukuba.ac.jp> References: <87bp5xg2b2.fsf@uwakimon.sk.tsukuba.ac.jp> <87wrokegq0.fsf@uwakimon.sk.tsukuba.ac.jp> <87k4kkdzkm.fsf@uwakimon.sk.tsukuba.ac.jp> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1289490736 29513 80.91.229.12 (11 Nov 2010 15:52:16 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 11 Nov 2010 15:52:16 +0000 (UTC) Cc: monnier@IRO.UMontreal.CA, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Nov 11 16:52:12 2010 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1PGZRa-00005B-K1 for ged-emacs-devel@m.gmane.org; Thu, 11 Nov 2010 16:52:10 +0100 Original-Received: from localhost ([127.0.0.1]:51163 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PGZRZ-0004OV-RG for ged-emacs-devel@m.gmane.org; Thu, 11 Nov 2010 10:52:09 -0500 Original-Received: from [140.186.70.92] (port=35978 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PGZQQ-0003tL-9t for emacs-devel@gnu.org; Thu, 11 Nov 2010 10:50:59 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PGZQO-00050L-8e for emacs-devel@gnu.org; Thu, 11 Nov 2010 10:50:57 -0500 Original-Received: from imss12.cc.tsukuba.ac.jp ([130.158.254.161]:54933) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PGZQM-0004zd-MR; Thu, 11 Nov 2010 10:50:55 -0500 Original-Received: from imss12.cc.tsukuba.ac.jp (imss12.cc.tsukuba.ac.jp [127.0.0.1]) by postfix.imss71 (Postfix) with ESMTP id 2821B2AF547; Fri, 12 Nov 2010 00:50:51 +0900 (JST) Original-Received: from mgmt1.sk.tsukuba.ac.jp (unknown [130.158.97.223]) by imss12.cc.tsukuba.ac.jp (Postfix) with ESMTP id 183372AF542; Fri, 12 Nov 2010 00:50:51 +0900 (JST) Original-Received: from uwakimon.sk.tsukuba.ac.jp (uwakimon.sk.tsukuba.ac.jp [130.158.99.156]) by mgmt1.sk.tsukuba.ac.jp (Postfix) with ESMTP id 237303FA0513; Thu, 11 Nov 2010 21:27:07 +0900 (JST) Original-Received: by uwakimon.sk.tsukuba.ac.jp (Postfix, from userid 1000) id 860DA11FBD2; Thu, 11 Nov 2010 21:29:17 +0900 (JST) In-Reply-To: X-Mailer: VM undefined under 21.5 (beta29) "garbanzo" ed3b274cc037 XEmacs Lucid (x86_64-unknown-linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:132544 Archived-At: Eli Zaretskii writes: > ??? Which part of design of bzr won't permit me doing the > following? Eli, I have no idea how you could possibly think that's an appropriate question at this point in the thread (and the same goes for several of your following comments), so I'm going to quit while I'm ahead. However, in considering how to reply, I did come up with one suggestion possibly worthy of consideration. > The issue of whether to have configure in the repository is a separate > one. If the decision is not to track it, then, of course, all of the > above is not relevant. Obviously, configure *is* in the repo. Then you either do something to prevent the problems I described, or sooner or later they arise. The obvious thing to do is to run autoconf, then commit configure along with configure.in. To keep Glenn happy, maybe the Bazaar guys can come up with a plugin or a patch that allows you to configure files that should never be diffed unless you ask for it (like binaries, you just get a stanza in the diff that says the files differ but the diff itself is omitted because the file appears in .diffignore or diff.ignore= in .bzr/config). That likely won't be too hard, because they have to do something more complex to avoid spewing binary garbage, anyway. So there is some place where bzr is going, "oh, let's not display the diff of this file" and suppressing either the diff operation itself or the output. Quite likely it's a couple of lines to change to add this feature.