unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@ics.uci.edu>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: Chong Yidong <cyd@stupidchicken.com>, emacs-devel@gnu.org
Subject: Re: moving SCCS later in vc-handled-backends
Date: Tue, 23 Jun 2009 23:52:32 -0700 (PDT)	[thread overview]
Message-ID: <200906240652.n5O6qWAh026050@godzilla.ics.uci.edu> (raw)
In-Reply-To: <87y6rixjcs.fsf@uwakimon.sk.tsukuba.ac.jp> (Stephen J. Turnbull's message of "Wed, 24 Jun 2009 14:59:31 +0900")

"Stephen J. Turnbull" <stephen@xemacs.org> writes:

  > Dan Nicolaescu writes:
  > 
  >  > Can you please give some more details here?
  > 
  > I just read the docs, which claim there is a good reason for file-
  > oriented VCSes to come first.  If the docs are wrong, they should be
  > fixed.
  > 
  > As far as I know this has always been rare.  The whole idea is quite
  > possibly obsolete according to what you say about the actual behavior
  > of vc, but if anybody still cares the change you're suggesting will be
  > a subtle change in behavior that will be intermittent and possibly
  > hard to diagnose.  I've found that it's almost always better to change
  > DWIM to "do nothing" as opposed to "do what somebody else means".

Why intermittent?  It's quite deterministic, and it matters if and only
if the same file is registered by SCCS and another backend.

SCCS by itself is rare, using both SCCS and another VCS on the same file
gotta be even less frequent.

  >  > An example would be even better.
  >  > vc does not decide a file is controlled by some VCS just based on the
  >  > presence of a directory, it actually tries to see if that file is
  >  > controlled by that VCS.
  >  > The ordering matters when the same file is controlled by multiple VCS,
  >  > vc will choose the first one in vc-handled-backends.
  > 
  > AFAIK it will also do this if it's controlled by no backend, too.

True, but in that case the order of search is irrelevant the same result
if obtained all the time: no backend claims to be responsible.




  parent reply	other threads:[~2009-06-24  6:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-23  7:01 moving SCCS later in vc-handled-backends Dan Nicolaescu
2009-06-23  7:17 ` Rob Weir
2009-06-23  8:31 ` Stephen J. Turnbull
2009-06-23 14:06   ` Chong Yidong
2009-06-23 18:44     ` Stephen J. Turnbull
2009-06-23 19:09       ` Dan Nicolaescu
2009-06-24  5:59         ` Stephen J. Turnbull
2009-06-24  6:18           ` Jason Rumney
2009-06-24  6:52           ` Dan Nicolaescu [this message]
2009-06-24  7:51             ` tomas
2009-06-24 14:58               ` Dan Nicolaescu
2009-06-24 22:46             ` Stephen J. Turnbull
2009-06-24 21:41   ` Stefan Monnier

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=200906240652.n5O6qWAh026050@godzilla.ics.uci.edu \
    --to=dann@ics.uci.edu \
    --cc=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    --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).