From: Andre Spiegel <spiegel@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: vc-cvs-stay-local vs vc-stay-local
Date: Mon, 10 Apr 2006 01:05:07 +0100 [thread overview]
Message-ID: <1144627507.5901.9.camel@localhost> (raw)
In-Reply-To: <u3bgm8k49.fsf@jasonrumney.net>
On Sun, 2006-04-09 at 23:22 +0100, Jason Rumney wrote:
> Do we need both these variables? If so, the way they interact with
> each other is not at all clear, so the doc strings need some work.
Thanks for the hint. vc-stay-local is supposed to be a global setting,
and vc-cvs-stay-local, if defined, is supposed to override it for CVS
only. The problem is that currently both variables are defined via
defcustom, and so vc-cvs-stay-local always overrides whatever you
specify in vc-stay-local.
This needs to be fixed, you are right. I'm thinking about a solution.
prev parent reply other threads:[~2006-04-10 0:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-09 22:22 vc-cvs-stay-local vs vc-stay-local Jason Rumney
2006-04-10 0:05 ` Andre Spiegel [this message]
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=1144627507.5901.9.camel@localhost \
--to=spiegel@gnu.org \
--cc=emacs-devel@gnu.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).