From: Stefan Monnier <monnier@iro.umontreal.ca>
To: esr@thyrsus.com
Cc: "Eric S. Raymond" <esr@snark.thyrsus.com>,
Dan Nicolaescu <dann@ics.uci.edu>,
emacs-devel@gnu.org
Subject: Re: vc-directory breakage
Date: Tue, 06 May 2008 21:30:19 -0400 [thread overview]
Message-ID: <jwv63tqkipt.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <20080506082112.GC23773@thyrsus.com> (Eric S. Raymond's message of "Tue, 6 May 2008 04:21:12 -0400")
>> 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
next prev parent reply other threads:[~2008-05-07 1:30 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-05 15:21 vc-directory breakage Eric S. Raymond
2008-05-05 15:32 ` David Kastrup
2008-05-05 15:39 ` Bastien Guerry
2008-05-05 15:45 ` David Kastrup
2008-05-05 15:52 ` Juanma Barranquero
2008-05-05 16:03 ` David Kastrup
2008-05-05 16:23 ` Bastien Guerry
2008-05-05 16:40 ` David Kastrup
2008-05-05 16:50 ` Lennart Borgman (gmail)
2008-05-05 17:00 ` Bastien Guerry
2008-05-05 20:14 ` Juanma Barranquero
2008-05-05 22:09 ` Thomas Lord
2008-05-05 22:17 ` Stephen J. Turnbull
2008-05-06 0:04 ` Eric S. Raymond
2008-05-06 0:36 ` Dan Nicolaescu
2008-05-06 0:48 ` Eric S. Raymond
2008-05-06 1:03 ` Stefan Monnier
2008-05-06 8:21 ` Eric S. Raymond
2008-05-06 9:08 ` David Kastrup
2008-05-06 16:34 ` Dan Nicolaescu
2008-05-07 1:30 ` Stefan Monnier [this message]
2008-05-06 1:10 ` Dan Nicolaescu
2008-05-06 9:01 ` Eric S. Raymond
2008-05-06 12:03 ` Dan Nicolaescu
2008-05-06 16:03 ` Eric S. Raymond
2008-05-06 6:36 ` David Kastrup
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwv63tqkipt.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=dann@ics.uci.edu \
--cc=emacs-devel@gnu.org \
--cc=esr@snark.thyrsus.com \
--cc=esr@thyrsus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).