From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Dan Nicolaescu <dann@ics.uci.edu>
Cc: 2756@emacsbugs.donarmstrong.com
Subject: bug#2756: move SCCS later in vc-handled-backends
Date: Mon, 23 Mar 2009 18:15:00 -0400 [thread overview]
Message-ID: <jwvskl399a2.fsf-monnier+emacsbugreports@gnu.org> (raw)
In-Reply-To: <200903232151.n2NLpuHT014920@godzilla.ics.uci.edu> (Dan Nicolaescu's message of "Mon, 23 Mar 2009 14:51:56 -0700 (PDT)")
>> > SCCS should be moved after later in the vc-handled-backends list, after
>> > the modern VCs.
>> > Opening any file costs a call to vc-sccs-registered
>> > vc-sccs-search-project-dir (and whatever they call).
>>
>> No matter where SCCS is in the vc-handled-backends list, those functions
>> will be run for any file that is not version controlled, which is likely
>> to be a very common case.
>>
>> > SCCS is not really popular nowadays,
>>
>> Same thing for RCS, indeed.
>>
>> > and that should be reflected on the vc-handled-backends list.
>>
>> We could remove backends from the list based on the presence/absence of
>> the corresponding executable(s).
> Would that be acceptable for 23.1?
No.
> If not, let's go for fixing the easier problem: moving SCCS later in the
> list of backends.
What problem? And in what way is it a fix for it?
Stefan
next prev parent reply other threads:[~2009-03-23 22:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200908261834.n7QIYhVX023388@godzilla.ics.uci.edu>
2009-03-23 17:25 ` bug#2756: move SCCS later in vc-handled-backends Dan Nicolaescu
2009-03-23 20:16 ` Stefan Monnier
2009-03-23 21:51 ` Dan Nicolaescu
2009-03-23 22:15 ` Stefan Monnier [this message]
2009-03-23 22:22 ` Dan Nicolaescu
2009-03-23 23:50 ` Stefan Monnier
2009-04-01 15:44 ` Dan Nicolaescu
2009-04-01 15:55 ` Stefan Monnier
2009-08-26 18:40 ` bug#2756: marked as done (move SCCS later in vc-handled-backends) Emacs bug Tracking System
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=jwvskl399a2.fsf-monnier+emacsbugreports@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=2756@emacsbugs.donarmstrong.com \
--cc=dann@ics.uci.edu \
/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).