From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Paul R <paul.r.ml@gmail.com>
Cc: esr@thyrsus.com, "Eric S. Raymond" <esr@snark.thyrsus.com>,
"Stephen J. Turnbull" <stephen@xemacs.org>,
emacs-devel@gnu.org
Subject: Re: Ready to start serious work on VC mode again
Date: Fri, 02 May 2008 10:27:27 -0400 [thread overview]
Message-ID: <jwvd4o4ye92.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87prs5vqrm.fsf@gmail.com> (Paul R.'s message of "Thu, 01 May 2008 20:11:09 +0200")
>> > Multiple back ends is kind of a wacky edge case;
>>
>> I don't agree. Multiple back end workspaces are going to be quite
>> common *among the population of people who are likely to turn into
>> vc.el hackers*. DAK obviously uses them, I do, Barry Warsaw (Mailman
>> maintainer and Python release engineer) uses them on at least three
>> projects, and that's just a few folks I know.
>>
>> You want this feature to shine, I think.
> Does anybody have a clear idea about how VC should behave in such a
> situation ?
Currently, there are 2 ways to control it:
- vc-handled-backends whose order influences which backend is used
by default.
- C-x v b which allows you to switch to another backend.
The fact that backends are currently associated to filenames is the
source of the problems we need. They should be associated to
buffers instead.
Stefan
next prev parent reply other threads:[~2008-05-02 14:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-28 18:19 Ready to start serious work on VC mode again Eric S. Raymond
2008-04-28 19:32 ` Jason Earl
2008-04-28 19:56 ` Eric S. Raymond
2008-04-28 21:05 ` Jason Earl
2008-04-28 23:33 ` Andreas Schwab
2008-04-28 23:40 ` Stephen J. Turnbull
2008-04-29 2:19 ` Eric S. Raymond
2008-04-30 12:24 ` David Kastrup
2008-05-01 8:09 ` Eric S. Raymond
2008-05-01 9:27 ` Nick Roberts
2008-05-01 16:01 ` Eric S. Raymond
2008-05-01 16:42 ` Stephen J. Turnbull
2008-05-01 18:11 ` Paul R
2008-05-01 19:44 ` Sean O'Rourke
2008-05-01 19:54 ` David Kastrup
2008-05-02 14:27 ` Stefan Monnier [this message]
2008-05-02 14:32 ` David Kastrup
2008-05-02 19:24 ` Eric S. Raymond
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=jwvd4o4ye92.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=esr@snark.thyrsus.com \
--cc=esr@thyrsus.com \
--cc=paul.r.ml@gmail.com \
--cc=stephen@xemacs.org \
/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).