unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lekktu@gmail.com>
Cc: Andre Spiegel <spiegel@gnu.org>, emacs-devel@gnu.org
Subject: Re: vc-cvs-global-switches and -f
Date: Wed, 22 Jun 2005 15:03:40 +0200	[thread overview]
Message-ID: <f7ccd24b0506220603694a5b82@mail.gmail.com> (raw)
In-Reply-To: <87mzpir59n.fsf-monnier+emacs@gnu.org>

> I'm curious why you think so.  What kind of settings do you put in ~/.cvsrc?
> The nature of the ~/.cvsrc file is to contain settings which should
> basically always apply.

Nothing special:

cvs -z9
diff -u2
tag -c
edit -c
update -dP
release -d
status -v

"release -d", for example, is something I don't want a program to do
for me, only when I explicitly type "cvs remove xxxx" on the command
line.

As I said earlier in the thread, this does not cause a problem for me;
I have my customizations on .emacs and .cvsrc, and I knew enough to do
M-x set-variable vc-cvs-global-options '("-f"). It just strikes me as
a bad default.

> BTW, I consider it a bug in CVS that it complains
> when ~/.cvsrc says -u but the command line says -c (or vice-versa): the
> command line arg should take precedence.

Yes, I agree with that. But even if it didn't complain, I would still
think the same (but I wouldn't have realized VC was using .cvsrc :-)

-- 
                    /L/e/k/t/u

      reply	other threads:[~2005-06-22 13:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-21  1:28 vc-cvs-global-switches and -f Juanma Barranquero
2005-06-21 20:49 ` Stefan Monnier
2005-06-21 22:24   ` Juanma Barranquero
2005-06-22  3:31     ` Stefan Monnier
2005-06-22  3:51       ` Juanma Barranquero
2005-06-22 10:08         ` Andre Spiegel
2005-06-22 10:41           ` Juanma Barranquero
2005-06-22 11:48             ` Andre Spiegel
2005-06-22 11:48             ` Stefan Monnier
2005-06-22 13:03               ` Juanma Barranquero [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=f7ccd24b0506220603694a5b82@mail.gmail.com \
    --to=lekktu@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=spiegel@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).