From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: vc-directory breakage Date: Tue, 06 May 2008 21:30:19 -0400 Message-ID: References: <20080505152149.E5BB99F054B@snark.thyrsus.com> <857ie8ahr3.fsf@lola.goethe.zz> <20080506000456.GA14206@thyrsus.com> <200805060036.m460aVto021222@sallyv1.ics.uci.edu> <20080506004849.GA14523@thyrsus.com> <20080506082112.GC23773@thyrsus.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1210123836 32464 80.91.229.12 (7 May 2008 01:30:36 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 7 May 2008 01:30:36 +0000 (UTC) Cc: "Eric S. Raymond" , Dan Nicolaescu , emacs-devel@gnu.org To: esr@thyrsus.com Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed May 07 03:31:11 2008 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.50) id 1JtYUu-0006Zb-OD for ged-emacs-devel@m.gmane.org; Wed, 07 May 2008 03:31:09 +0200 Original-Received: from localhost ([127.0.0.1]:53369 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JtYUC-0006eO-RV for ged-emacs-devel@m.gmane.org; Tue, 06 May 2008 21:30:24 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JtYU9-0006eJ-VN for emacs-devel@gnu.org; Tue, 06 May 2008 21:30:21 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JtYU8-0006e6-Ep for emacs-devel@gnu.org; Tue, 06 May 2008 21:30:20 -0400 Original-Received: from [199.232.76.173] (port=36594 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JtYU8-0006e3-7l for emacs-devel@gnu.org; Tue, 06 May 2008 21:30:20 -0400 Original-Received: from ironport2-out.pppoe.ca ([206.248.154.182] helo=ironport2-out.teksavvy.com) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JtYU7-0005mG-Uy for emacs-devel@gnu.org; Tue, 06 May 2008 21:30:20 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgoFAG+jIEhMCqqd/2dsb2JhbACBU6tS X-IronPort-AV: E=Sophos;i="4.27,445,1204520400"; d="scan'208";a="20002293" Original-Received: from smtp.pppoe.ca (HELO smtp.teksavvy.com) ([65.39.196.238]) by ironport2-out.teksavvy.com with ESMTP; 06 May 2008 21:30:19 -0400 Original-Received: from pastel.home ([76.10.170.157]) by smtp.teksavvy.com (Internet Mail Server v1.0) with ESMTP id NGL48419; Tue, 06 May 2008 21:30:19 -0400 Original-Received: by pastel.home (Postfix, from userid 20848) id 0D97A8E5F; Tue, 6 May 2008 21:30:19 -0400 (EDT) In-Reply-To: <20080506082112.GC23773@thyrsus.com> (Eric S. Raymond's message of "Tue, 6 May 2008 04:21:12 -0400") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) X-detected-kernel: by monty-python.gnu.org: Genre and OS details not recognized. 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:96624 Archived-At: >> I believe you have misunderstood the request, then: "support the multi-VCS >> case" means exactly what Dan asks, which is "make sure only one backend >> is used for a given command, even if the command includes files that are >> under various backends". >> >> I.e. the issue is not "several subdirs of *vc-dir* which each use >> a different backend", but "all the files under *vc-dir* are under the >> control of several backends at the same time". > I understood the second part. But your first paragraph leaves me > more confused than I was before. > It is already the case that "only one backend is used for a given > command, even if the command includes files that are under various > backends". If a fileset is not all owned by the same backend, a > consistency check in vc-deduce-fileset will fail. Why should it fail? > What I don't see is what any of this has to do with keeping a buffer-local > backend variable per directory, which is what Dan is saying he wants. It's not per-directory. It's per-buffer. This way, there is no need to check consistency within vc-deduce-fileset: it's consistent by construction. > By hypothesis, backend is a per-*file* property. Let's say I have a tree in ~/foo that's under both CVS and Arch. Let's say I open a vc-dir on ~/foo where I want to see the Arch state. Now let's say I also open the file ~/foo/toto.c and choose the CVS backend in that buffer. With the per-file backend you have the problem that ~/foo/titi.c is (presumably) using Arch whereas ~/foo/toto.c is using CVS, so your `diff' operation in the ~/foo vc-dir will fail complaining of an inconsistent fileset. With the per-buffer backend, there is no such problem. Stefan