From: Glenn Morris <rgm@gnu.org>
To: Lars Magne Ingebrigtsen <lmi@gnus.org>
Cc: 8179@debbugs.gnu.org
Subject: bug#8179: 24.0.50; vc thinks that SVN takes care of all my files
Date: Tue, 15 Mar 2011 14:41:37 -0400 [thread overview]
Message-ID: <kcsjuo8bvi.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <m3hbb4dzx2.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Tue, 15 Mar 2011 19:03:21 +0100")
Lars Magne Ingebrigtsen wrote:
> Are all these VCs really that, er, difficult to determine whether they
> are in effect or not? I thought they all pretty much used a .git (or
> the like) in the current directory, but that's obviously wrong...
We're only talking about unregistered files, right?
For registered files, it should get it correct every time.
For unregistered files, IIUC it effectively does:
(for backend in BACKENDS ...
(for directory in PWD PARENTS ... )
rather than:
(for directory in PWD PARENTS ... )
(for backend in BACKENDS ... )
I agree that the second method does seem more sensible on the face of
it, but the former is the documented way it works.
It may to some extent be an artifact of the basic design dating from the
days when you had eg a CVS directory in every directory. The "modern"
VCS have eg a single .bzr in the parent directory, not one in every
subdir as well.
Well, actually I think the doc is misleading too:
"Registering a File for Version Control"
If the file's directory already contains files registered in a
version control system, Emacs uses that system. If there is more than
one system in use for a directory, Emacs uses the one that appears
first in @code{vc-handled-backends}.
I don't think the first sentence is correct.
Anyway, I think investigating if it can be made to work the other way
would be a worthwhile experiment.
next prev parent reply other threads:[~2011-03-15 18:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-05 12:13 bug#8179: 24.0.50; vc thinks that SVN takes care of all my files Lars Magne Ingebrigtsen
2011-03-07 23:46 ` Glenn Morris
[not found] ` <mailman.0.1299542816.10278.bug-gnu-emacs@gnu.org>
2011-03-08 9:43 ` Lars Magne Ingebrigtsen
2011-03-08 17:50 ` Glenn Morris
2011-03-08 21:15 ` Stefan Monnier
[not found] ` <mailman.7.1299607619.4046.bug-gnu-emacs@gnu.org>
2011-03-15 15:34 ` Lars Magne Ingebrigtsen
2011-03-15 17:18 ` Glenn Morris
2011-03-16 15:49 ` Dan Nicolaescu
[not found] ` <mailman.4.1300210622.26153.bug-gnu-emacs@gnu.org>
2011-03-15 18:03 ` Lars Magne Ingebrigtsen
2011-03-15 18:41 ` Glenn Morris [this message]
2011-03-15 20:37 ` Lars Magne Ingebrigtsen
2011-03-15 19:04 ` Stefan Monnier
2011-03-15 19:35 ` Glenn Morris
2011-03-16 0:46 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=kcsjuo8bvi.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=8179@debbugs.gnu.org \
--cc=lmi@gnus.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.