* bug#2756: move SCCS later in vc-handled-backends @ 2009-03-23 17:25 ` Dan Nicolaescu 2009-03-23 20:16 ` Stefan Monnier 2009-08-26 18:40 ` bug#2756: marked as done (move SCCS later in vc-handled-backends) Emacs bug Tracking System 0 siblings, 2 replies; 9+ messages in thread From: Dan Nicolaescu @ 2009-03-23 17:25 UTC (permalink / raw) To: bug-gnu-emacs 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). SCCS is not really popular nowadays, and that should be reflected on the vc-handled-backends list. ^ permalink raw reply [flat|nested] 9+ messages in thread
* bug#2756: move SCCS later in vc-handled-backends 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-08-26 18:40 ` bug#2756: marked as done (move SCCS later in vc-handled-backends) Emacs bug Tracking System 1 sibling, 1 reply; 9+ messages in thread From: Stefan Monnier @ 2009-03-23 20:16 UTC (permalink / raw) To: Dan Nicolaescu; +Cc: 2756, bug-gnu-emacs > 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). Stefan ^ permalink raw reply [flat|nested] 9+ messages in thread
* bug#2756: move SCCS later in vc-handled-backends 2009-03-23 20:16 ` Stefan Monnier @ 2009-03-23 21:51 ` Dan Nicolaescu 2009-03-23 22:15 ` Stefan Monnier 0 siblings, 1 reply; 9+ messages in thread From: Dan Nicolaescu @ 2009-03-23 21:51 UTC (permalink / raw) To: Stefan Monnier; +Cc: 2756 Stefan Monnier <monnier@IRO.UMontreal.CA> writes: > > 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? If not, let's go for fixing the easier problem: moving SCCS later in the list of backends. ^ permalink raw reply [flat|nested] 9+ messages in thread
* bug#2756: move SCCS later in vc-handled-backends 2009-03-23 21:51 ` Dan Nicolaescu @ 2009-03-23 22:15 ` Stefan Monnier 2009-03-23 22:22 ` Dan Nicolaescu 0 siblings, 1 reply; 9+ messages in thread From: Stefan Monnier @ 2009-03-23 22:15 UTC (permalink / raw) To: Dan Nicolaescu; +Cc: 2756 >> > 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 ^ permalink raw reply [flat|nested] 9+ messages in thread
* bug#2756: move SCCS later in vc-handled-backends 2009-03-23 22:15 ` Stefan Monnier @ 2009-03-23 22:22 ` Dan Nicolaescu 2009-03-23 23:50 ` Stefan Monnier 0 siblings, 1 reply; 9+ messages in thread From: Dan Nicolaescu @ 2009-03-23 22:22 UTC (permalink / raw) To: Stefan Monnier; +Cc: 2756 Stefan Monnier <monnier@iro.umontreal.ca> writes: > What problem? And in what way is it a fix for it? The fact that SCCS generates unnecessary work for all files managed by bzr, git, hg (which is a good number nowadays). ^ permalink raw reply [flat|nested] 9+ messages in thread
* bug#2756: move SCCS later in vc-handled-backends 2009-03-23 22:22 ` Dan Nicolaescu @ 2009-03-23 23:50 ` Stefan Monnier 2009-04-01 15:44 ` Dan Nicolaescu 0 siblings, 1 reply; 9+ messages in thread From: Stefan Monnier @ 2009-03-23 23:50 UTC (permalink / raw) To: Dan Nicolaescu; +Cc: 2756 >> What problem? And in what way is it a fix for it? > The fact that SCCS generates unnecessary work for all files managed by > bzr, git, hg (which is a good number nowadays). Unnecessary work is not a problem in and of itself. And, if this unnecessary work is a problem for Bzr, Git, or Hg files, it's even more problematic for all the non-revision controlled files which additionally need to do unnecessary work to determine that they're neither under Git, Bzr, nor Hg control. So changing the order won't make much of a difference, other than hide the problem in the particular case where you're lucky enough to access a file under the right VCS. Stefan ^ permalink raw reply [flat|nested] 9+ messages in thread
* bug#2756: move SCCS later in vc-handled-backends 2009-03-23 23:50 ` Stefan Monnier @ 2009-04-01 15:44 ` Dan Nicolaescu 2009-04-01 15:55 ` Stefan Monnier 0 siblings, 1 reply; 9+ messages in thread From: Dan Nicolaescu @ 2009-04-01 15:44 UTC (permalink / raw) To: Stefan Monnier; +Cc: 2756 Stefan Monnier <monnier@iro.umontreal.ca> writes: > >> What problem? And in what way is it a fix for it? > > The fact that SCCS generates unnecessary work for all files managed by > > bzr, git, hg (which is a good number nowadays). > > Unnecessary work is not a problem in and of itself. No, but given that it's unnecessary, and that it will be unnecessary in the future too, why not get rid of it? > And, if this unnecessary work is a problem for Bzr, Git, or Hg files, > it's even more problematic for all the non-revision controlled files > which additionally need to do unnecessary work to determine that they're > neither under Git, Bzr, nor Hg control. So changing the order won't > make much of a difference, other than hide the problem in the particular > case where you're lucky enough to access a file under the right VCS. Yes, the thing is, what you are talking about above is a separate problem that cannot be solved at this point. Even more, the solution for that problem would not solve the problem or unnecessary checking for SCCS for systems that have sccs installed by default (i.e. about all commercial unixes and free ones that install cssc). So why not just move SCCS to the end of the list? ^ permalink raw reply [flat|nested] 9+ messages in thread
* bug#2756: move SCCS later in vc-handled-backends 2009-04-01 15:44 ` Dan Nicolaescu @ 2009-04-01 15:55 ` Stefan Monnier 0 siblings, 0 replies; 9+ messages in thread From: Stefan Monnier @ 2009-04-01 15:55 UTC (permalink / raw) To: Dan Nicolaescu; +Cc: 2756 >> >> What problem? And in what way is it a fix for it? >> > The fact that SCCS generates unnecessary work for all files managed by >> > bzr, git, hg (which is a good number nowadays). >> Unnecessary work is not a problem in and of itself. > No, but given that it's unnecessary, and that it will be unnecessary in > the future too, why not get rid of it? >> And, if this unnecessary work is a problem for Bzr, Git, or Hg files, >> it's even more problematic for all the non-revision controlled files >> which additionally need to do unnecessary work to determine that they're >> neither under Git, Bzr, nor Hg control. So changing the order won't >> make much of a difference, other than hide the problem in the particular >> case where you're lucky enough to access a file under the right VCS. > Yes, the thing is, what you are talking about above is a separate problem > that cannot be solved at this point. > Even more, the solution for that problem would not solve the problem or > unnecessary checking for SCCS for systems that have sccs installed by > default (i.e. about all commercial unixes and free ones that install > cssc). So why not just move SCCS to the end of the list? Because we're in prestest so we limit ourselves to bug-fixes. Stefan ^ permalink raw reply [flat|nested] 9+ messages in thread
* bug#2756: marked as done (move SCCS later in vc-handled-backends) 2009-03-23 17:25 ` bug#2756: move SCCS later in vc-handled-backends Dan Nicolaescu 2009-03-23 20:16 ` Stefan Monnier @ 2009-08-26 18:40 ` Emacs bug Tracking System 1 sibling, 0 replies; 9+ messages in thread From: Emacs bug Tracking System @ 2009-08-26 18:40 UTC (permalink / raw) To: Dan Nicolaescu [-- Attachment #1: Type: text/plain, Size: 898 bytes --] Your message dated Wed, 26 Aug 2009 11:34:43 -0700 (PDT) with message-id <200908261834.n7QIYhVX023388@godzilla.ics.uci.edu> and subject line Re: bug#2756: move SCCS later in vc-handled-backends has caused the Emacs bug report #2756, regarding move SCCS later in vc-handled-backends to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@emacsbugs.donarmstrong.com immediately.) -- 2756: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=2756 Emacs Bug Tracking System Contact owner@emacsbugs.donarmstrong.com with problems [-- Attachment #2: Type: message/rfc822, Size: 2786 bytes --] From: Dan Nicolaescu <dann@ics.uci.edu> To: bug-gnu-emacs <bug-gnu-emacs@gnu.org> Subject: move SCCS later in vc-handled-backends Date: Mon, 23 Mar 2009 10:25:21 -0700 (PDT) Message-ID: <200903231725.n2NHPLF1011557@godzilla.ics.uci.edu> 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). SCCS is not really popular nowadays, and that should be reflected on the vc-handled-backends list. [-- Attachment #3: Type: message/rfc822, Size: 2325 bytes --] From: Dan Nicolaescu <dann@ics.uci.edu> To: 2756-done@emacsbugs.donarmstrong.com Subject: Re: bug#2756: move SCCS later in vc-handled-backends Date: Wed, 26 Aug 2009 11:34:43 -0700 (PDT) Message-ID: <200908261834.n7QIYhVX023388@godzilla.ics.uci.edu> Dan Nicolaescu <dann@ics.uci.edu> writes: > 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). > > SCCS is not really popular nowadays, and that should be reflected on the > vc-handled-backends list. Closing, this request has been rejected. ^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2009-08-26 18:40 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[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
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
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).